Using database backup add-in
What is the database backup add-in?
Use this add-in to automatically back up your database on a schedule of your choosing.
Cloud 66 supports two types of backups: managed and unmanaged.
Using managed backups has several benefits:
- You can download database backups through the web UI and API
- Backup verifiers ensure that your backups actually contain what you expect
- Use database replication to scale your databases
- You can easily restore database backups
- Stored in Cloud 66 storage
The 100 most recent managed backups are kept by default.
Unmanaged backups are stored on your local server and are available under
/var/cloud66/backups. The 10 most recent unmanaged backups are kept by default.
In order for backups to work, you are required to have twice as much space on your server as your backup consumes.
We charge per GB (or part thereof) of data stored. See our pricing page for the most up to date price.
The backup format for redis and mongodb is always binary. For MySQL and Postgresql you can choose between binary and text.
A binary backup is a snapshot of the data folder of your database service along with necessary log files. The result is a data folder which can be restored on your server to return it to the same state as it was at the time of backup.
As this backup contains raw data of your database server (rather than a human readable SQL dump file) you can expect much faster backup/restore process, particularly for large databases. This method can be up to 4 times faster which can be very helpful in failover scenarios. But there are some limitations:
- You cannot restore it on a server with different version of the database engine
- You cannot use it on slave servers
- You cannot use it on servers with data folders symlinked to other locations
- You cannot use it on encrypted databases
- You need to shut down the database service during the restore
For this format we generate a dump file with SQL commands that, when fed back to the server, will recreate the database in the same state as it was at the time of the dump.
As the output of the backup is a simple SQL dump file, you can use it to import your data to other servers or when you want to upgrade your server version but restore process will be much longer than binary, particularly if you have lots of indexes in your database.
These are other benefits of this type of backup:
- You can restore this backup while the server is running.
- You can move backup jobs to your slave servers (if available) to reduce your master server load
You can specify how often you would like to backup your database. Your options are:
You can specify whether or not you would like to Gzip compress your backups. Compressing your backups will take up less space, but will require additional processing during the compression.
This option only applies to text MySQL and PostgreSQL backups. You can provide a comma separated list of tables which you want to exclude from your backup to create a smaller one.
Install on replica
This option only applies to text MySQL and PostgreSQL and to redis (binary) backups. With this option you can move the backup service to your database replica if available, to relieve pressure on your production database.
Adding or removing a Postgresql binary backup requires a service restart.
Restoring database backups
We recommend using the automated restore process to restore backups. To do this:
- Open your Cloud 66 Dashboard and click on the app in question
- Click on the link to your backups in the Add-ins panel
- Click on the “database symbol” icon next to the backup you want to restore
- Confirm the action
If you need to manually download and/or restore a backup, please read our in-depth guide on manually managing database backups.
Backup storage locations
We store your backups in the closest possible AWS region to your servers. At the moment we store data in the following regions: