Your data is your responsibility. MapleDeploy snapshots are a safety net, not a replacement for your own database backups. For production databases, set up Coolify's S3 backup feature.
Setting up Coolify database backups
Coolify has built-in support for automated database backups to any S3-compatible storage. It supports PostgreSQL, MySQL, MariaDB, and MongoDB. This is the recommended way to protect your databases.
Step 1: Choose an S3 provider
Any S3-compatible storage will work, including AWS S3, eazyBackup e3 (Canadian), or whichever provider you prefer.
Step 2: Add S3 storage in Coolify
In Coolify, go to Storage and select New Storage. Set Type to S3 and give the storage a name.
Enter the S3 details from your storage provider:
- Host (the endpoint)
- Bucket
- Region
- Access key
- Secret key
Then select Validate Connection & Continue, which tests the connection before the storage is saved.
Step 3: Configure database backup
Open your database resource in Coolify, then open Backups.
Set:
- The S3 storage destination.
- A backup schedule. Use daily backups for production databases.
- A retention count, such as the last 14 backups.
Enable the backup after those settings are saved.
Step 4: Test your backup
After setting up, trigger a manual backup and verify the file appears in your S3 bucket, the file size is reasonable (not empty), and you can download and open it.
Backing up volumes and directories
Not all of your data is in a database. Uploaded files, SQLite databases and other application data live in persistent volumes and directory mounts. Coolify can back these up on a schedule too.
Set up a storage backup
Open your application or service in Coolify, then open Persistent Storage. In the row for the volume or directory you want to protect, select the backup icon (Configure volume backup). The resource's Backups page lists every schedule, and you can add new ones there too.
Set:
- A frequency:
hourly,daily,weekly, or a cron expression. - The archive behavior. Keep containers running avoids downtime, but files that change during the backup can be archived in an inconsistent state. Stop containers during archive gives a consistent copy, and the application is unavailable until the archive is written.
- A timeout, in seconds.
Then select Enable Backup. Back Up Now runs one straight away.
Send storage backups to S3
By default, archives are kept on your server. To keep a copy off the server, add an S3 storage under Storage as described above, then select Enable S3 on the backup and choose one or more storages. Each backup is uploaded to every storage you select. Under Local copy, choose Delete after S3 upload if you don't want archives kept on the server.
Set retention
Local and S3 archives each have three limits: Backups to keep, Days to keep and Maximum storage (GB). The first limit reached removes the oldest archive. Use 0 for no limit.
Check your storage backups
Open the schedule's executions to see each run's status, size and time. From there you can download an archive or delete it.
Restoring from backup
Use Coolify's import or restore flow when available. If you restore manually, PostgreSQL custom-format backups use pg_restore, MySQL or MariaDB use mysql or mariadb, and MongoDB uses mongorestore.
To restore a MapleDeploy VM snapshot after active-server corruption or post-cancellation recovery, contact hello@mapledeploy.ca. We can restore from the latest available recovery snapshot: the latest weekly snapshot for active-server disaster recovery, or the pre-deletion snapshot retained for 30 days after cancellation.
Restoring a volume or directory
Coolify has no restore button for storage backups. Each archive is a .tar.gz of the volume's contents, so you restore it by extracting it back into the volume:
- Stop the application or service in Coolify.
- Open your server's Terminal in Coolify (owners and admins can use it). Local archives are under
/data/coolify/backups/volumes/. To find them, runfind /data/coolify/backups/volumes -name '*.tar.gz'. If the archive you need is only in S3, copy it to the server first. - Extract the archive into the volume with the command below, using the volume name shown in Persistent Storage.
- Start the application or service again and check your data.
docker run --rm -v <volume-name>:/volume -v <archive-folder>:/backup:ro alpine tar -xzf /backup/<archive-file> -C /volume
For a directory mount, extract the archive into that directory on the server instead. Extracting does not remove files created after the backup, so empty the volume first if you need an exact copy.
MapleDeploy snapshots
MapleDeploy takes weekly snapshots of your entire VM, including the OS, Coolify, Docker containers, volumes, and databases. We also take a snapshot before any VM termination.
After cancellation, snapshots are kept for 30 days on our Canadian infrastructure in Toronto. Only MapleDeploy staff can access them, and only to fulfill a restore request from the verified account holder. Snapshots use our infrastructure provider's volume snapshot system. After 30 days, they are permanently deleted.
Snapshots are point-in-time copies and can be up to 7 days old. They are intended for disaster recovery, not granular database restores.
Best practices
Use these defaults for production data:
- Back up at least daily.
- Back up the volumes that hold application data, not just the databases.
- Keep at least 14 to 30 days of backups.
- Store backups in a separate S3 bucket, away from your production server.
- Test restores periodically, not just backup creation.
- Check Coolify's backup logs so failures do not go unnoticed.