iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
Coolify cannot currently send backups directly to Google Drive as a documented native destination. Its supported remote target is S3-compatible storage. The dependable pattern is to configure Coolify’s local and/or S3 backups, verify that those files can be restored, and then copy the verified artifacts to Google Drive with a separately maintained transfer or synchronization process.
This distinction matters: an instance backup protects Coolify’s own configuration and deployment metadata, while database backups protect database contents. Neither automatically includes files, volumes, or data inside your deployed applications. Those items need their own backup method.
What “back up Coolify to Google Drive” actually involves
There are two different backup scopes in a Coolify installation, and treating them as one is the most common cause of an incomplete recovery plan.
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 a backup of the Coolify control plane, not a complete copy of every application managed by that control plane.
#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.
In particular, an instance backup does not include data inside deployed applications, database contents, or persistent volumes. Restoring the instance can recreate Coolify’s configuration, but it cannot recreate application data that was never included in the backup.
Database backups
Each supported database needs a separate schedule. Coolify’s engine-aware database workflow supports PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite. You configure these jobs from each database’s Backups page.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Redis, Dragonfly, and KeyDB are outside that scheduled workflow. Their persistence and backup process must be designed separately, using the method appropriate to each deployment.
Application files and volumes
Persistent application files and mounted volumes are not covered by the instance backup. If an application stores uploads, generated media, certificates, or other state in a volume, create a separate file-level or volume-level backup and send that copy off the server. A Google Drive copy of a Coolify database dump does not substitute for a volume backup.
How Coolify’s backup architecture works
Coolify creates a backup file locally on the server. For a database job, the database dump must be created successfully before Coolify uploads that local file to the selected S3-compatible destination. If the upload fails, the local file can remain and the execution reports a remote-storage warning.
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.
Coolify can remove the local copy only after a successful S3 upload. Local retention and S3 retention are independent, so decide how long each location should retain files rather than assuming one policy controls both.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11The S3 target must already exist. Coolify requests an endpoint, bucket name, region, access key, and secret key, then validates the connection. Documented examples include Amazon S3, Cloudflare R2, and Supabase Storage; other S3-compatible services can also work when they meet Coolify’s connection requirements.
Destination comparison
| Destination | Native Coolify role | Off-site copy | Retention responsibility | Recovery consideration |
|---|---|---|---|---|
| Server-local storage | Where Coolify creates the backup first | No; it remains on the Coolify server | Coolify’s local retention setting | Unavailable if the server and its storage are lost |
| S3-compatible storage | Supported remote destination | Yes, when the service is outside the server | Coolify’s S3 retention setting, independent of local retention | Can be retrieved during a server outage if credentials and the service are available |
| Google Drive through an external bridge | Not a documented native Coolify destination | Yes, after a separate copy or synchronization succeeds | Managed by the transfer process and Google Drive policy | Depends on the bridge, its credentials, and a tested download or restore path |
Do not describe the Google Drive step as a Coolify feature. It is an additional dependency that must be monitored and tested independently.
Prepare before enabling backups
Complete these checks before creating schedules:
- Confirm that you can sign in to the self-hosted Coolify instance with an account allowed to change backup settings.
- Choose whether to retain a local copy, an S3 copy, or both while you validate the process. Keeping a local copy until the remote path has been verified gives you a recovery option if the first upload or transfer fails.
- Create the S3-compatible bucket and credentials before entering them in Coolify. Use credentials limited to the required bucket where your storage service supports that restriction.
- Measure available disk space on the Coolify server. A database dump is created locally before remote upload, so the server needs room for the dump and any retained local copies.
- List every deployed database and identify its engine. Supported engines use Coolify’s scheduled workflow; Redis, Dragonfly, and KeyDB require a different persistence or backup design.
- Decide where the Coolify
APP_KEYwill be stored outside the server. Without it, restored secrets cannot be read. - Choose a disposable database or isolated environment in which to perform a restore test. A successful backup job alone does not prove that the backup is usable.
Step 1: Configure the Coolify instance backup
- In a self-hosted Coolify installation, open Settings > Backup.
- Set the instance-backup schedule appropriate to how often your projects, resources, settings, and deployment history change.
- Set local retention. Retention controls how many or how much of the locally created backup history Coolify keeps according to the options shown in your installation.
- If you are using an S3-compatible destination, enter its endpoint, bucket name, region, access key, and secret key.
- Run the connection validation. Do not proceed on the assumption that an endpoint is compatible; wait for Coolify to confirm the connection.
- Enable the remote copy if your plan is to use S3 as the primary off-site store.
- Keep a local copy during initial verification. After you have downloaded and inspected a remote object and completed a restore test, you can reduce local retention if disk space requires it.
The instance backup is only the control-plane portion of the plan. Continue with database schedules and any application-volume method you need.
Step 2: Preserve the APP_KEY separately
Save the complete APP_KEY=... line in a password manager or another secure location that is not the Coolify server. Coolify states that restored secrets cannot be read without this key. An S3 instance backup contains the database backup file; it does not remove the need to preserve the key independently.
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.
Store the key with the recovery information for the S3 bucket and the Google Drive account, but do not place it in a public document or an unprotected folder. Test that the person responsible for recovery can retrieve it without logging in to the failed Coolify server.
Step 3: Schedule every supported database
- Open the database resource in Coolify and select its Backups page.
- Add a backup schedule.
- Choose the database scope to dump. Check the scope carefully when an instance contains more than one database.
- Set the database retention policy.
- Select the S3-compatible storage target that you validated in Coolify.
- Save the schedule and observe at least one execution before treating the job as operational.
A database job runs only while the database is running. If the database is stopped when the schedule fires, the expected dump will not be produced. Include the database’s run state in your monitoring checks.
Engines outside the scheduled workflow
Redis, Dragonfly, and KeyDB do not use Coolify’s engine-aware scheduled database-backup workflow described above. Configure persistence and backup for those services separately, then send the resulting files to your chosen off-site destination. Do not infer coverage for them from a successful PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, or SQLite job.
Step 4: Copy verified backup files to Google Drive
Because Google Drive is not listed as a native Coolify target, the Drive copy must run outside Coolify. Use a separately maintained transfer or synchronization process that can read the verified local or S3 artifact and write it to the intended Google Drive folder.
- Choose the source of truth for the transfer: the local Coolify backup directory or the S3-compatible object. S3 is generally the better source when you want the Drive process to continue working after the Coolify server is unavailable, but it adds another credential and retrieval dependency.
- Create a dedicated Google Drive folder for backup artifacts. Keep access limited to the people and service account that perform recovery.
- Configure the external transfer process with the minimum permissions needed to read the source and write to that folder.
- Copy only files that have completed successfully. A process that starts copying a file while Coolify is still writing it can create an incomplete Drive object.
- Preserve useful metadata in the filename or folder structure, such as the Coolify instance, database scope, and creation time. Do not alter the original backup contents.
- Define how old Drive copies are removed. Coolify’s local and S3 retention settings do not automatically enforce a Google Drive retention policy.
- Run the transfer manually once, inspect the resulting Drive file, and then enable its recurring schedule.
Coolify’s documentation does not name a Google Drive connector or guarantee that Drive can serve as an S3 endpoint. Treat any gateway or synchronization product as an independent component: evaluate its current documentation, secure its credentials, monitor failures, and verify that it can download an object for restoration.
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.
Verify every backup execution
Use a checklist for both the Coolify job and the external Drive copy:
- The Coolify execution is marked successful rather than merely scheduled.
- The database was running when its job executed.
- The recorded database scope is the one you intended to protect.
- The generated file has a size greater than zero.
- The S3 upload reports success when remote storage is enabled.
- If the S3 upload failed, the local copy is still present and has been preserved for investigation.
- The external process copied the completed artifact, not a partial file.
- The Google Drive object can be downloaded with the credentials reserved for recovery.
Keep execution logs and transfer logs together long enough to investigate a missed schedule. A green Coolify job does not prove that the later Drive copy succeeded, and a file visible in Drive does not prove that its database contents can be restored.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Perform a disposable restore test
Recovery validation is a separate operation from backup creation. Coolify’s own guidance emphasizes that a backup is not a restore test.
- Select a recent artifact from Google Drive or the S3-compatible source and download it to an isolated recovery workspace.
- Confirm that the file is complete and that you have the matching
APP_KEY=...line available for an instance recovery. - Restore a database copy into a disposable database environment, not the production database.
- Connect a test copy of the application to that database and verify that it can read the expected schema and representative records.
- For an instance backup, restore into an isolated Coolify environment and confirm that projects, resources, settings, and deployment history are present and that encrypted secrets can be read with the preserved APP_KEY.
- Record how long the download and restore took, which credentials were needed, and any manual steps. Use those observations to improve the recovery runbook.
Repeat the test after changing the external transfer process, the S3 endpoint, database engines, or the Coolify version. A process can continue producing files while becoming impossible to restore because of a changed credential, missing key, or incorrect scope.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Back up volumes and application data separately
Application volumes need their own method because they are outside both the Coolify instance backup and the scheduled database workflow. First identify which services write persistent data to volumes. Then select a file or volume backup process that can create a consistent copy, retain it off the server, and restore it into an isolated location.
Best Value
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Do not assume that exporting a database covers uploaded files, generated assets, or configuration files stored beside the database. Conversely, a volume copy does not replace the database dump or the Coolify instance backup. Recovery requires all three scopes when an application depends on all three.
Recommended Free Tools
Troubleshooting common failures
The Google Drive copy is empty or missing
Check the external transfer log first. Then confirm that the source file exists, has a non-zero size, and was closed before copying. If the S3 upload failed, use the retained local file while you repair the S3 credentials or endpoint. Do not delete the local copy until one complete artifact is available elsewhere.
Coolify reports a remote-storage warning
The dump may have succeeded even though the S3 upload did not. Check for the local artifact, inspect the endpoint, bucket, region, access key, and secret key, and rerun validation. Once the remote upload succeeds, verify the object independently before allowing local retention to remove the local file.
A scheduled database backup did not run
Confirm that the database was running at the scheduled time and that the schedule is attached to the intended database scope. Review the execution history for the resource rather than relying on the existence of an older file.
Restored secrets cannot be read
Locate the separately stored complete APP_KEY=... line. The key is required to decrypt restored secrets. If it was not preserved outside the server, the backup file alone cannot supply it.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteThe file downloads but the restore fails
Check that you downloaded the completed artifact, not a partial Drive copy, and that the restore target uses the correct database engine and scope. Repeat the test from the original S3 object or retained local file to determine whether the failure was introduced during the external transfer.
A practical operating policy
For a small installation, a resilient arrangement is to keep short-term local copies, send Coolify’s instance and supported database backups to an S3-compatible target, and copy verified objects to Google Drive for an additional off-site copy. Document the three scopes—instance, databases, and volumes—so a future operator does not mistake one for another.
For every schedule, assign an owner for checking successful execution, S3 upload status, Drive transfer status, and periodic restore tests. Keep the APP_KEY and storage credentials in secure locations separate from the server. During an outage, the recovery order is to obtain the required artifacts and credentials, restore the Coolify control plane if needed, restore databases, restore volumes, and then reconnect applications and verify their data.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
