Data loss is something, which can happen to everybody: be it an unpatched security hole in your underlying CMS or be it the overworked content editor, who accidentally deletes rather important data. Whatever the cause, you should have backups to recover in case of disaster. Backups are notoriously underused, because it can be hard to set them up properly and also hard to monitor them continuously, to guarantee that they are there, when needed.
Automatic, out-of-the box, off-site, encrypted daily MySQL backups, without configuration and without hassle.
MySQL Backups are not included with all database plans. See our pricing page for more.
- Daily backups
- 30 days retention
- Zero downtime
- No performance impact on live database
- end-to-end encrypted transport
- AES-256 encrypted storage
- Stored in a non-public S3 bucket
- Easy access from the Dashboard
- Unlimited backup storage size
Find them in the Dashboard > Your App > Backups. There you can download gzipped
sql files, containing the result of a
mysqldump of your App's database.
If you need backups available for a longer time period than the retention time allows (see specs page), we recommend to periodically download the backups from the dashboard and store them locally.
The MySQL backup file is a regular MySQL dump, generated by the
mysqldump tool. You can recover from it the same way you would (re-)import MySQL data into your database. Please read on in the MySQL import/export guide.
No file backups with Pro Apps¶
Unlike with Universal Apps — there are no file backups with Pro Apps. The implicit reason is that the file system contents of Pro Apps are ephemeral and deployments atomic. So the contents of the file system can always be regenerated with the contents of the Git repository. So file backups for Pro Apps are not required. The Git repo is the file backup.