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 Settings > S3 Storages and select Add Storage.
Enter the S3 details from your storage provider:
- Endpoint
- Access key
- Secret key
- Bucket name
Test the connection before you continue.
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.
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.
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 with encryption at rest. 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 databases:
- Back up at least daily.
- 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.