Back up environments
When you’re making changes to your apps, you want to be sure those changes only improve things and don’t make you lose any data. You also want to have a disaster recovery plan in place. Backups help you protect yourself against potential data loss.
Backups represent a complete snapshot of an environment’s data. This includes all persistent data from all running services and any files stored on mounts. The snapshot is stored internally and can’t be downloaded. Code is managed through Git and so isn’t included. You can restore previous code using Git commands such as revert.
You might want to make backups of your live environment before merging a different environment into it or each time you increase the storage space of your services.
You also have regularly scheduled automated backups of your production environments to cover most cases.
You can only backup and restore active environments. To work with an inactive environment, first activate it.
To back up an environment, you need an Admin role for that environment type.
By default, triggering a manual backup causes a momentary pause in site availability so that all requests can complete. This means the environment is backed up in a known consistent state. The total interruption is usually only 15 to 30 seconds. Any requests during that time are held temporarily, not dropped.
To avoid this downtime, use live backups.
For consistent backups, create the backups during non-peak hours for your site.
For information on how long backups are retained, see the data retention policy.
Backups for Dedicated environments have a specific frequency.
On Grid environments, non-Production environments can have up to 2 manual backups. The number of available backups for Production environments depends on your schedule.
|Schedule||Manual backups||Automated backups|
|Advanced||4||21: daily, weekly, and monthly|
|Premium||4||44: 6-hourly, daily, and monthly|
The schedules available to you depend on your tier.
|Tier||Default schedule||Possible upgrade|
An upgrade comes at an additional cost. The exact cost depends on the size of your storage.
To upgrade to the higher schedule, follow these steps:
- In the Console, navigate to the project where you want to change the schedule.
- Click Settings.
- Click Edit plan.
- For Backups, click the name of your current schedule. If clicking has no effect, you are already on the highest available schedule.
- Select the target schedule.
- Click Save.
To downgrade to the lower schedule, contact support.
For Dedicated environments, see more about backups of Dedicated environments.
For Grid environments, automated backups are taken for Production environments at least once every day. The exact number of backups depends on your backup schedule.
Daily backups are taken at around 4:00 every day based on the project timezone. The time for 6-hourly backups is based on the daily backup.
Automated backups are always live.
Live automated backups are available on all regions except the legacy regions:
These regions will be upgraded in the future. If you’re on one of these regions and want live automated backups now, migrate your project to a newer region.
You can create backups without any downtime. This means your environment is running and open to connections during the backup.
Because the connections may come in during backup creation, live backups may have data inconsistencies among containers. They may make restorations less reliable. To avoid such issues, schedule manual backups during non-peak hours, when the short amount of downtime is least noticed.
You can create a manual live backup on a Grid project:
platform backup:create --live
Live backups are available on all regions except the legacy regions:
These regions will be upgraded in the future. If you’re on one of these regions and want live backups now, migrate your project to a newer region.
- Navigate to the environment you want to back up.
- Click Backups.
- Click Backup.
- Click Backup.
You can also automate the process of creating manual backups through cron jobs. The cron job uses the CLI command to back up the environment. It requires you to set up the CLI on the environment with an API token.
Although this process is automated, backups created in this way count as manual for the backup schedule. They don’t affect the automated backups taken as part of the schedule.
Backups are stored as binary large objects separate from your environments. This storage is replicated over multiple data centers in different locations. This means that in the rare event a data center becomes unavailable, your backups are still available.