Backups
Daily database backups, off-server copies and how long they're kept.
Sites with a database hold real data: orders, form entries, accounts. airepeat sets up Coolify's own backups for them and records every run.
Daily database backupsLink to this section: Daily database backups
Turn on backups from the site's database row. Coolify then backs up the database every day at 03:00 UTC, takes the first backup straight away, and keeps backups for 7, 14 or 30 days. Setting it up is free and needs no approval, because it only adds copies.
Daily backups cover PostgreSQL, MySQL and MariaDB. Redis is never backed up: it only holds data the site can rebuild.
Every half hour airepeat reads the schedule's runs and adds each one to the site's backup history.
Off-server copiesLink to this section: Off-server copies
To keep copies elsewhere, add an S3-compatible bucket, such as Cloudflare R2, as an S3 storage in your Coolify, so its keys never reach airepeat. Then choose Copy backups off the server on the site. New schedules copy each backup there from the start and keep it for 30 days.
RestoringLink to this section: Restoring
Restores of database backups are done in Coolify today; airepeat points you there.
WordPress sitesLink to this section: WordPress sites
A WordPress site's database and uploads live inside its Coolify service. Before you purge one, export a full WordPress backup; airepeat asks you to confirm you have.
Archive before purgeLink to this section: Archive before purge
Deleting a site is two steps. It's archived first, and only purged after 7 days, with a separate approval.