Back up and restore
Scheduled, verified backups to your own storage.
1Add a destination
Infrastructure → Backups → Add destination. Give S3-compatible storage you own (a bucket, its endpoint and keys); we check we can write to it before saving. Each website gets its own encrypted restic repository there.
2Schedule backups
On the website’s Backups tab, choose Schedule backups: how often, the time (UTC) and how many snapshots to keep. Each backup holds the database, the .env file and shared storage, and is checked after it’s written. Back up now takes one straight away.
3Restore
Choose Restore on a backup in the website’s Backups tab. The website is in maintenance mode meanwhile, and put back as it was if any step fails. Infrastructure → Backups lists recent backups across the project.
4A second copy
When scheduling backups, choose Also copy to for a second destination (another provider or region). Each backup is sent there too, for a 3-2-1 setup; the backup list shows whether the second copy was made.
5Restore drills
Leave Monthly restore drill ticked and, once a month, the latest backup is restored into a scratch area on the server and checked (the database loads and the app starts), then cleaned up. If it fails, the account’s owners are emailed.