Coolify does not document Google Drive as a native backup destination. Its supported remote path is local backup creation followed by upload to an S3-compatible storage target. To keep copies in Google Drive, configure and verify Coolify’s local and/or S3 backups first, then use a separately maintained transfer or synchronization process to copy those files to Drive. Treat that bridge as an external dependency, not as a Coolify feature.
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, application volumes, and secrets are different recovery assets. A backup job that finishes successfully is not proof that you can restore the service.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What Coolify can back up
Start by defining the recovery scope. Coolify has separate mechanisms for its own configuration and for supported database engines.
Coolify instance backup
An instance backup protects Coolify’s projects, resources, settings, and deployment history. Self-hosted installations configure it at Settings > Backup. It does not include data stored inside deployed applications, databases, or persistent volumes. Those items require their own backup procedures.
#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.
Coolify’s documentation also warns that an S3 instance backup contains only the database backup file. Preserve the encryption key separately: without the complete APP_KEY=... line, restored secrets cannot be read.
Database backups
Each database needs its own schedule. Coolify’s engine-aware workflow supports:
- PostgreSQL
- MySQL
- MariaDB
- MongoDB
- ClickHouse
- SQLite
Redis, Dragonfly, and KeyDB are not covered by that scheduled workflow. Use each engine’s own persistence or backup method, and include the resulting files or snapshots in your off-site-copy plan.
Application files and volumes
Files uploaded to an application, user-generated media, configuration files mounted from a volume, and other persistent volume contents are outside both the Coolify instance backup and an engine-aware database dump. Inventory these paths separately. A Google Drive copy of Coolify’s backup artifact cannot recover volume data that was never included in the artifact.
Make a recovery inventory before scheduling
List every item that must exist after a rebuild: the Coolify instance data, each database resource, persistent volumes, uploaded files, deployment configuration, external credentials, and the matching APP_KEY. Mark the owner and backup method for each item. This prevents a common mistake: declaring the system protected because one database file appears in Drive while a critical media volume has no copy at all.
How Coolify’s native backup path works
Coolify creates the backup on the server first. For a database job, the database is dumped to a local file; after the dump succeeds, Coolify uploads that file to the selected S3-compatible destination.
- If the remote upload fails, the local file can remain and the execution reports a remote-storage warning.
- Coolify can remove the local copy only after a successful S3 upload.
- Local retention and S3 retention are independent settings.
- A database job runs only while the database is running.
The S3 destination must already exist. Coolify asks for an endpoint, bucket name, region, access key, and secret key, then validates the connection. Official examples include Amazon S3, Cloudflare R2, and Supabase Storage; other services are usable when they provide a compatible S3 API.
Think of the process as two checkpoints: dump creation and remote upload. A successful first checkpoint gives you a local artifact; only a successful second checkpoint gives you a verified remote artifact. Your Google Drive process should copy files only after the relevant checkpoint has succeeded.
Destination choices for a Google Drive requirement
| Destination | Coolify support | Off-site copy | Retention | Outage retrieval | Operational requirement |
|---|---|---|---|---|---|
| Server-local storage | Native first step | No; it is on the Coolify server | Configured locally | Unavailable if the server and its disks are lost | Keep enough disk space and monitor job results |
| S3-compatible storage | Native remote destination | Yes, when the service is separate from the server | Independent from local retention | Download the object from the storage service during an outage | Validate endpoint, bucket, region, and credentials; verify every upload |
| Google Drive | Not documented as a native Coolify target | Yes, after an external copy or synchronization succeeds | Controlled by the external Drive process | Depends on the bridge, Drive access, and a tested download | Maintain, monitor, secure, and restore-test the external process |
Do not assume that a Google Drive gateway can act as Coolify’s S3 endpoint. The reviewed Coolify documentation neither names a Google Drive connector nor guarantees Drive compatibility as an S3 endpoint. Build the Drive step after a verified local or S3 artifact exists.
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 primary recovery source deliberately. S3 is the directly supported Coolify destination and is usually the simplest source for an automated download. Drive can serve as a second off-site copy, but retrieval depends on the transfer tool, Drive permissions, quota, network access, and the ability to download a complete file. Whichever source is your emergency choice, test that exact source rather than assuming another copy behaves identically.
Step-by-step: create a Coolify backup that can be copied to Drive
1. Configure the instance backup
- In a self-hosted Coolify installation, open Settings > Backup.
- Choose a schedule appropriate to the amount of configuration change you can tolerate losing.
- Set local retention so several known-good files remain available while you validate the remote path.
- If you will use an S3-compatible destination, enter its endpoint, bucket name, region, access key, and secret key.
- Run Coolify’s connection validation and enable the remote copy only after the validation succeeds.
- Keep a local copy until you have downloaded the remote object and confirmed that it opens as a non-empty backup file.
Never delete the only local copy merely because a job reports that it uploaded. Confirm the object in the remote storage service and check its size first.
2. Preserve the APP_KEY outside the server
- Locate the installation’s complete
APP_KEY=...setting. - Copy the entire line exactly, including the prefix and value.
- Store it in a password manager or another encrypted location that is not dependent on the Coolify server.
- Restrict access to the people who would perform a restoration.
The key is a recovery prerequisite. A database backup without the matching key may contain encrypted secrets that cannot be read after restoration. Keep the key under a separate failure domain from the server and from the backup files.
Do not place the key in the same Drive folder as an unrestricted backup or commit it to a repository. Record who can retrieve it, how access is audited, and how the restoration operator will receive it during an outage. If the key is rotated, document which key belongs to which backup period and test a newly created backup after the change.
3. Schedule every supported database
Open the Backups page for each database resource and create a job.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Add a schedule for the database.
- Select the intended database scope rather than assuming the whole server is included.
- Set retention for the local and, where configured, S3 copies.
- Select the validated S3 storage target.
- Confirm that the database remains running at the scheduled time.
- Run or wait for an execution and inspect its result before relying on automation.
Repeat this for every PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite resource that must be recoverable. Handle Redis, Dragonfly, and KeyDB separately because they do not use this Coolify database-backup workflow.
Check scope explicitly. A job attached to one database resource does not automatically cover another resource, even when both run on the same server. Name files or destination folders so that the engine, resource, and creation time are apparent to the person performing recovery.
4. Build the Google Drive copy outside Coolify
Use a separately maintained transfer or synchronization process to copy a verified local or S3 backup artifact into Google Drive. The process should:
- Authenticate to Drive with a credential that is not hard-coded into application files.
- Read only the backup directory or objects required for the transfer.
- Preserve the original filename, timestamp, and database scope so an operator can identify the correct restore point.
- Upload to a restricted Drive folder rather than a shared public location.
- Report failures distinctly from Coolify’s own backup status.
- Retain more than one restore point and remove old Drive files according to an explicit retention policy.
- Confirm that an upload is complete before deleting a source file or marking the run successful.
There are two practical source patterns. A local-source process watches or reads the backup directory on the Coolify server. An S3-source process downloads verified objects from the remote bucket before uploading them to Drive. The S3-source pattern keeps the transfer independent of the Coolify host, but it still requires working storage credentials and a tested download path.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
Do not describe either pattern as a built-in integration. If the external process stops, Coolify can continue reporting successful local backups while the Google Drive copy becomes stale.
Give the bridge its own health check. Monitor the age of the newest Drive file, not just whether the transfer process is running. A process can remain active while losing permission, filling its working disk, or repeatedly skipping files. Alert when no new copy appears within the interval your recovery plan allows.
5. Verify each execution
For every scheduled run, check the Coolify execution details and the destination object. A useful verification checklist is:
- The execution status is successful, not merely scheduled.
- The database scope and resource name are correct.
- The resulting file exists and has a size greater than zero.
- The S3 upload is successful when remote storage is enabled.
- The external Drive process reports a successful upload.
- The Drive file can be listed and downloaded with the recovery account.
- The downloaded byte count matches the uploaded artifact or otherwise passes the transfer tool’s integrity check.
An upload warning means the remote copy is not yet a recovery copy. Keep the local artifact, investigate credentials, endpoint, permissions, connectivity, and available space, and retry before allowing retention to remove it.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →6. Perform a disposable restore test
- Choose a backup file from the destination you intend to rely on during an outage.
- Download it to a disposable environment or temporary database location.
- Restore it into a database that is not serving production traffic.
- Supply the preserved
APP_KEYwhen restoring Coolify data that contains encrypted secrets. - Connect a test instance of the application to the restored database.
- Check representative records, authentication, migrations, and application reads.
- Record the time required, the commands or UI actions used, and any missing volume or secret dependencies.
A successful backup job proves that a file was produced. It does not prove that the file is complete, decryptable, readable by the database engine, or usable by the application.
Repeat this exercise after changing the Coolify version, database engine, S3 provider, Drive transfer tool, credentials, or retention rules. A restore procedure that worked before a change is evidence for the old configuration, not a guarantee for the new one.
How to plan retention and recovery
Keep independent retention layers
Coolify’s local and S3 retention settings operate independently, and the Google Drive copy has its own retention behavior. Decide how many restore points each layer should keep rather than assuming one setting controls all three. Keep at least one recent point and older points that cover the period in which corruption or accidental deletion could go unnoticed.
When disk space is limited, do not immediately set local retention to zero. First verify that the S3 object is present, non-empty, downloadable, and restorable. Only then should you allow successful remote uploads to trigger local cleanup.
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 errorsRetention is also a naming problem. Preserve enough metadata in filenames, folders, or an accompanying inventory to distinguish instance backups from database dumps and to identify the database scope. Never prune files solely by a generic name when multiple resources share the same folder.
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.
Use a recovery order
Document which destination is authoritative during an outage:
- Attempt retrieval from the validated S3 object if the S3 service is available.
- Use the Google Drive copy when the external bridge and Drive credentials are available.
- Use the server-local file only when the server and its storage remain trustworthy.
This order is a policy choice, not a Coolify setting. Whichever source you choose, perform restore tests from that exact source and account.
Protect credentials and keys
- Limit S3 access to the required bucket and backup operations.
- Protect the Google Drive transfer credential and avoid embedding it in a repository or public script.
- Store the Coolify
APP_KEYoutside the server and outside the same single storage location as the backup. - Rotate credentials through a documented procedure that includes updating the transfer process and testing a new backup.
- Ensure the recovery operator can access credentials without relying on the failed Coolify host.
Common failure cases
“Google Drive is not available in the backup destination list”
That is expected under the documented Coolify workflow. Configure local storage and, if desired, an S3-compatible target, then perform the Drive upload externally. Do not enter arbitrary Drive URLs into the S3 endpoint field unless the gateway’s current documentation explicitly confirms S3 compatibility and you have completed a real restore test.
The S3 upload fails but the job created a file
Keep the local file. Inspect the endpoint, bucket, region, access key, secret key, network route, permissions, and bucket capacity. The failed remote upload should be treated as a warning that off-site protection is incomplete, even though a local artifact exists.
The database job produces nothing
Confirm that the database resource was running at the scheduled time, that the schedule is attached to the correct resource, and that the selected scope is correct. Then run another execution and check that the resulting file is non-empty.
The backup restores but the application is broken
Check whether the missing item is an application volume, uploaded file, unsupported database engine, external secret, or other data outside the instance/database backup scope. Add a separate backup method for that dependency and repeat the disposable restore test with the complete set of artifacts.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated 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 matchRestored secrets cannot be read
Verify that the exact original APP_KEY=... line was preserved. Without the matching key, encrypted secrets in the restored data cannot be read. Do not overwrite the stored key while troubleshooting; first identify which key was used when the backup was created.
The Drive copy is old even though Coolify is green
Coolify reports its own backup workflow, not the health of an external synchronization process. Check the bridge’s logs, Drive permissions, quota, source path, and last successful upload time. Keep the newest verified local or S3 artifact while repairing the bridge and do not let cleanup remove it prematurely.
A file is present in Drive but cannot be restored
Download it again using the recovery account and compare it with the source artifact. An incomplete transfer, wrong database scope, missing APP_KEY, or unsupported application volume can all produce this symptom. Restore from S3 or local storage to determine whether the problem is the file itself or the Drive transfer.
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.
A workable Google Drive operating procedure
For a small self-hosted deployment, the following sequence keeps responsibilities clear:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- Coolify creates the instance and database backup locally.
- Coolify uploads the database artifact to a validated S3-compatible destination.
- An external process copies the verified artifact from local storage or S3 into a restricted Google Drive folder.
- Monitoring records failures from both Coolify and the external process.
- An operator periodically downloads a Drive file and restores it to a disposable database.
- The operator records the restore result and updates the procedure when Coolify, the database engine, credentials, or transfer process changes.
Add a short runbook next to the monitoring alerts. It should identify the Coolify host, S3 bucket and region, Drive folder, credential owners, APP_KEY location, supported database resources, volume backup method, and the last successful restore date. During an incident, this removes guesswork and prevents an operator from treating a stale Drive file as current.
This arrangement gives you an off-site Google Drive copy without claiming unsupported native integration. It also leaves a directly supported S3 path available when Drive access is unavailable.
Frequently Asked Questions
Can Coolify back up directly to Google Drive?
Not according to Coolify’s documented backup destinations. Coolify creates backups locally and can upload them to S3-compatible storage. Copy a verified local or S3 artifact to Google Drive with a separately maintained transfer or synchronization process.
What does a Coolify instance backup include?
It protects Coolify projects, resources, settings, and deployment history. It does not include data inside deployed applications, databases, or persistent volumes, which need separate backup procedures.
Free tools Windows power users keep installed
One-click scans. No signup required.
Where should I save the Coolify APP_KEY?
Save the complete APP_KEY=... line in a secure password manager or another encrypted location outside the Coolify server and outside the sole backup location. Restored secrets cannot be read without the matching key.
Which databases can use Coolify’s scheduled backup workflow?
The documented engine-aware workflow supports PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite. Redis, Dragonfly, and KeyDB require their own persistence or backup method.
Why did Coolify create a file but report an upload warning?
The local dump succeeded but the S3 upload did not. Keep the local file, inspect endpoint, bucket, region, credentials, permissions, connectivity, and capacity, and retry before local retention removes the artifact.
How do I know a Google Drive copy is usable?
List and download it with the recovery account, confirm it is non-empty and complete, then restore it into a disposable database and test representative application reads. A successful upload alone is not a restore test.
Should I use local storage, S3, or Drive as my only backup?
Local storage is a native first step but fails with the server. S3 is Coolify’s supported remote destination. Drive can be an additional off-site copy through an external bridge. Keep independent retention and test the exact source you will use during an outage.
How do I back up application volumes and uploaded files?
Neither the Coolify instance backup nor a supported database dump automatically covers persistent volumes or application uploads. Inventory those paths and add a separate file or snapshot backup, then include them in the disposable restore test.
The Bottom Line
Google Drive is not a documented native Coolify backup target. The dependable design is to create and verify Coolify instance and database backups locally, use validated S3-compatible storage as Coolify’s supported remote destination, preserve the matching APP_KEY separately, and copy verified artifacts to Drive with an external process. Monitor both layers, back up volumes and unsupported database engines separately, and prove recovery with a disposable restore test.
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.
