Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Coolify does not document Google Drive as a native backup destination. Its supported remote destination is S3-compatible storage. To keep a copy in Google Drive, configure Coolify’s local and/or S3 backups first, then copy verified backup files to Drive with a separate transfer or synchronization process.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
This distinction matters because a Coolify instance backup, a database dump, and application files are different things. You must preserve the Coolify APP_KEY, schedule each supported database separately, and back up application volumes with a method outside Coolify’s built-in database workflow. Finally, perform a disposable restore test; a job that reports success is not proof that recovery will work.
As an Amazon Associate I earn from qualifying purchases.
Can Coolify back up directly to Google Drive?
Not according to Coolify’s documented backup destinations. Coolify creates backup files locally and can upload them to an S3-compatible target. Google Drive is not listed as a native connector, and the documentation does not guarantee that Drive can be used as an S3 endpoint.
The reliable design is therefore a two-stage path:
- Coolify creates and verifies a local backup, optionally uploading it to an S3-compatible bucket.
- A separately maintained process copies the verified artifact from the server or S3 storage into Google Drive.
Google Drive is an external copy in this arrangement, not a Coolify backup target. Treat the transfer tool, its credentials, its retention policy, and its error reporting as separate parts of your disaster-recovery system. If the transfer fails, Coolify cannot make that failure look like a successful native Drive backup.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
What a Coolify backup actually contains
Before choosing a destination, identify which data you are protecting. Coolify separates its own control-plane data from the data used by deployed applications.
Coolify instance backup
An instance backup protects Coolify’s projects, resources, settings, and deployment history. Self-hosted installations configure this under Settings > Backup. It is the backup you need to rebuild Coolify’s configuration, but it does not include data inside deployed applications, application databases, or persistent volumes.
Database backups
Each database requires its own database-backup schedule. Coolify’s engine-aware scheduled workflow supports PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite. A database job runs only while that database is running.
Database backups are separate from the instance backup. Configure the scope, schedule, retention, and validated S3 destination from the database’s own Backups page. Do not assume that backing up the Coolify instance also dumps every database managed by that instance.
Application files and persistent volumes
Files stored in a deployed application’s volume are outside the instance-backup scope. They need a separate method appropriate to the application: for example, an application-level export, a filesystem copy, or storage snapshots. The method must account for data consistency; copying a live database volume without a database-aware procedure can produce an unusable set of files.
Redis, Dragonfly, and KeyDB
Redis, Dragonfly, and KeyDB do not use Coolify’s scheduled, engine-aware database-backup workflow described above. Give these services their own persistence and backup plan, then copy the resulting artifacts to your off-site destination if required.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Choose the backup path before adding Google Drive
Use Coolify’s supported path as the authoritative backup, and treat Drive as an additional copy. The following options describe what each location does in this design.
| Location | Coolify support | Off-site protection | Retention and deletion | Recovery consideration |
|---|---|---|---|---|
| Local server storage | Coolify creates backups locally. | None if the server is the only copy. | Set retention in the relevant Coolify backup settings. A local copy can remain when a remote upload fails. | Fast to retrieve while the server and its disk are available; lost with that server or disk. |
| S3-compatible storage | Supported remote destination for Coolify. | Yes, when the storage is separate from the Coolify host. | Local and S3 retention are independent. Coolify can remove the local copy only after a successful S3 upload. | Retrieve the object during a server outage if the S3 account and credentials remain available. |
| Google Drive copy | Not documented as a native Coolify destination. | Yes, if the transfer completes and the Drive account is independent of the server. | Controlled by the external transfer workflow and Drive; Coolify does not manage this copy. | Recovery depends on being able to authenticate to Drive and download an intact artifact. |
Do not make Drive the only copy until you have tested the complete path, including authentication and download during an outage scenario. A native S3 copy is easier to validate inside Coolify; Drive should add geographic or account separation rather than replace that validation.
Prepare the server and credentials
Complete these checks before creating schedules:
- Confirm that you are using a self-hosted Coolify installation if you expect to see Settings > Backup.
- Reserve sufficient local disk space for the largest instance and database artifacts. Coolify creates a local file before attempting a remote upload.
- Create the S3-compatible bucket first. Coolify expects an endpoint, bucket name, region, access key, and secret key, then validates the connection.
- Decide how long local and S3 copies should remain. Their retention settings are independent.
- Store the Coolify
APP_KEYoutside the server before relying on encrypted secrets in a recovery. - Decide where your Google Drive copy will be staged and who can operate the external transfer.
- Make a recovery account available for a disposable database restore.
Step 1: Configure the Coolify instance backup
- Sign in to the self-hosted Coolify dashboard.
- Open Settings > Backup.
- Set the instance-backup schedule and retention appropriate for your recovery-point objective.
- Configure the validated S3-compatible destination if you want Coolify to make an off-server copy.
- Enable the remote copy and keep a local copy until you have confirmed that the remote object exists and can be downloaded.
The instance backup covers Coolify’s projects, resources, settings, and deployment history. It is not a substitute for database schedules or volume backups. Keep those scopes visible in your operating checklist so an apparently healthy instance job does not create false confidence.
Step 2: Preserve the Coolify APP_KEY
Save the complete APP_KEY=... line in a password manager or another secure location that is not dependent on the Coolify server. Coolify states that restored secrets cannot be read without this key. An S3 instance-backup object contains the database backup file; it does not remove the need to preserve the key separately.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsProtect the key with the same care as the backup credentials. Do not leave it only in a server environment file that would disappear with the server, and do not paste it into the Google Drive folder as an unprotected text document. Your recovery procedure should specify who can retrieve the key and how access is audited.
Step 3: Configure each supported database
Repeat the following process for every database managed by Coolify:
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
- Open the database resource in Coolify.
- Open its Backups page.
- Add a schedule.
- Choose the database scope to dump.
- Set retention for the database artifacts.
- Select the validated S3-compatible storage target.
- Save the schedule and confirm that the database remains running when the job is expected to execute.
Coolify creates the dump locally first. After the dump succeeds, it uploads the local file to the selected S3-compatible target. If the upload fails, the local file may remain and the execution reports a remote-storage warning. That warning is not an off-site success; investigate it before allowing local retention to remove the only usable copy.
Engines covered by the scheduled workflow
| Engine | Coolify scheduled database backup |
|---|---|
| PostgreSQL | Supported |
| MySQL | Supported |
| MariaDB | Supported |
| MongoDB | Supported |
| ClickHouse | Supported |
| SQLite | Supported |
| Redis | Use a separate persistence or backup method |
| Dragonfly | Use a separate persistence or backup method |
| KeyDB | Use a separate persistence or backup method |
Step 4: Copy verified artifacts to Google Drive
Because Drive is not a documented Coolify destination, perform this step outside Coolify. You can manually download a verified local or S3 artifact and upload it to Drive, or operate a separately maintained synchronization process. The exact transfer utility is your operational choice; it must be able to authenticate to Drive, detect failed or partial uploads, and preserve the original file.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUse a controlled hand-off
- Wait for the Coolify execution to report success, and confirm the database scope that was dumped.
- Confirm that the local or S3 file exists and has a non-zero size.
- Download or export that exact artifact without renaming it in a way that loses its date, database identity, or retention context.
- Upload it to a Drive folder with restricted access.
- Check that Drive reports the upload as complete and that the stored size matches the source artifact.
- Record the artifact name, creation time, source location, and checksum if your transfer process supports checksums.
Do not configure an unverified Drive gateway as though it were an S3 endpoint. Such a gateway would be an additional product with its own compatibility and failure modes, not a feature guaranteed by Coolify’s documentation.
Step 5: Verify every execution
For each scheduled run, inspect more than the green status indicator. Verify all of the following:
- The run completed successfully rather than merely creating a local file.
- The intended database or instance scope is shown in the execution details.
- The artifact size is greater than zero and is plausible for that workload.
- The S3 upload succeeded when remote storage is enabled.
- The external Drive transfer completed and retained the full artifact.
- The local copy was deleted only under the retention behavior you intended.
Keep the logs or execution records needed to correlate a Coolify run with its S3 object and Drive copy. A Drive file with no known source run is difficult to trust during an incident.
Step 6: Perform a disposable restore test
Backup creation and recovery are separate operations. Coolify’s own guidance emphasizes that a backup is not a restore test. At a planned interval, choose a copy from S3 or Google Drive, restore it into a disposable database, and verify that the application can read the recovered data.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
- Retrieve the artifact using the same credentials and path you would use during an outage.
- Restore it into an isolated, disposable database rather than overwriting production.
- Supply the preserved
APP_KEYwhen restoring Coolify data so encrypted secrets can be read. - Check that expected projects, resources, settings, or rows are present, depending on the artifact tested.
- Point a test instance or application at the restored database and perform a representative read.
- Record the restore duration, any manual steps, and the artifact date.
If the restore fails, stop treating that backup chain as reliable. Correct the transfer, credentials, retention, or database procedure and run the test again with a newly generated artifact.
Back up application volumes separately
Persistent volumes and files created by applications are not included in a Coolify instance backup. A complete Google Drive strategy therefore needs a second workflow for those files.
For databases stored in volumes
Prefer the engine-aware dump produced by the database-backup workflow rather than copying raw files from a live volume. A raw volume copy can capture inconsistent pages or transaction state. If an application specifically requires filesystem snapshots, follow that application’s consistency procedure and test the resulting snapshot independently.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →For user uploads and documents
Identify the volume, pause writes or use the application’s export mechanism where necessary, create a consistent copy, and send that copy through the same verification and Drive-transfer stages. Keep volume artifacts distinguishable from Coolify instance and database artifacts so an operator does not restore the wrong type of file.
For Redis, Dragonfly, and KeyDB data
Choose the persistence or export mechanism supplied for the particular service, because Coolify’s scheduled database workflow does not cover these engines. Confirm that the resulting artifact can be loaded into a disposable service before depending on it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common failures
The S3 destination will not validate
Recheck the endpoint, bucket name, region, access key, and secret key. The target must already exist and accept the credentials. Until validation succeeds, retain local copies and do not describe the setup as off-site protected.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
The database job did not run
Confirm that the database resource was running at the scheduled time. Coolify’s database job runs only while the database is running. Also check the selected scope and the schedule on that database’s own Backups page.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The S3 upload failed but a local file remains
Preserve the local file, inspect the remote-storage warning, and correct the S3 connection before the next retention cycle. The remaining local file is useful for recovery, but it is not an off-site copy.
The Drive file is zero bytes or smaller than the source
Delete the incomplete Drive object, repeat the transfer from the verified local or S3 artifact, and compare source and destination sizes. Do not overwrite the source until the new Drive copy is complete.
Restored secrets cannot be read
Locate the separately stored complete APP_KEY=... line and use it during restoration. Possessing the backup file alone is insufficient for decrypting restored secrets.
The job says successful but the application cannot use the restore
Run a disposable restore and an application-level read. Investigate database scope, volume coverage, credentials, and consistency. A successful file creation or upload does not prove that the application state is recoverable.
A practical operating checklist
- Instance backup is scheduled under Settings > Backup.
- Every PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite resource has its own schedule.
- Redis, Dragonfly, and KeyDB have documented service-specific persistence or export procedures.
- The S3-compatible target is validated with its endpoint, bucket, region, access key, and secret key.
- Local and S3 retention settings are understood separately.
- The complete
APP_KEY=...line is stored outside the Coolify host. - Application volumes and user-upload data have a separate, consistency-aware backup.
- Each successful artifact is copied to Drive by an external process and checked for completeness.
- A disposable restore has been completed from an artifact retrieved through the intended recovery path.
With this arrangement, Coolify remains on its documented local-plus-S3 backup path, while Google Drive serves as a separately verified off-site copy. That separation keeps unsupported assumptions out of the recovery plan and makes each failure visible before an actual outage.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
