Your data is your responsibility. While we take weekly automated snapshots as a safety net, these are not a replacement for your own backup strategy. We strongly recommend setting up Coolify’s database backup feature.
What we back up
MapleDeploy takes automated weekly snapshots of your entire VM – your OS, Coolify, Docker containers, volumes, and databases. We also take a snapshot before any VM termination, with 30-day snapshot retention after cancellation.
These snapshots are a safety net for disaster recovery, but they have limitations – they’re point-in-time (up to 7 days old) and require contacting support to restore. For real-time or granular backups, use Coolify’s database 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 – AWS S3, eazyBackup e3 (Canadian), or whichever provider you prefer.
Step 2: Add S3 storage in Coolify
Go to your Coolify dashboard → Settings → S3 Storages, click “Add Storage”, enter your S3 credentials (endpoint, access key, secret key, bucket), and test the connection.
Step 3: Configure database backup
Open your database resource in Coolify and navigate to the “Backups” tab. Select your S3 storage destination, set a backup schedule (we recommend daily for production databases), configure retention (e.g., keep last 14 backups), and enable the backup.
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
To restore from a Coolify S3 backup, download the backup file from your S3 bucket, connect to your database using the credentials from Coolify, and restore using the appropriate command (psql, mysql, mongorestore).
To restore from a VM snapshot (after accidental deletion, corruption, etc.), contact hello@mapledeploy.ca. We can restore your server from the most recent weekly snapshot.
Best practices
Back up production databases daily at minimum, and periodically test your restores by downloading a backup and verifying you can actually restore from it. Store backups in a separate S3 bucket – don’t keep them on the same infrastructure as your production data. Set retention to at least 14–30 days to recover from delayed discovery of data corruption, and check Coolify’s backup logs periodically to make sure backups are succeeding.