Back up an environment
On this page
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.
You might want to create 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.
Note that you can only create backups and restore active environments. To work with an inactive environment, first activate it.
As an admin user, you can do a backup of your environment. This backup includes the complete data and code of the environment. All persistent data from all running services and any files stored on mounts are included. The backup is stored internally on Platform.sh. That is, the backup can be applied to environments on Platform.sh, but it can’t be downloaded. If you need to download backups, instead export your mount and service data).
You restore your environment using the backup. At this point, the data and code from the backup are restored to ensure a consistent state. The latest code in your repository may have been modified such that it no longer works correctly with the old, restored data.
Platform.sh does not modify your Git repository. Any further changes you make use the latest code in your repository.
Depending on your needs, you can do the following:
a) To use the code from the time of the backup as a baseline for future changes, make sure you restore it yourself in your Git repository. To do so, use Git commands such as
b) To use your latest code instead, just redeploy your environment or push a new change.
By default, creating 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, preview environments can have up to 2 manual backups. The number of available backups for Production environments depends on your schedule.
|2 daily backups (1 backup for each of the last 2 days)
|21 backups:- 6 daily backups (1 backup for each of the last 6 days) - 3 weekly backups (1 backup for each of the last 3 weeks)- 12 monthly backups (1 backup for each of the last 12 months)
|44 backups:- 3 backups for the last 24 hours- 30 daily backups (1 backup for each of the last 30 days)- 11 monthly backups (1 backup for each of the last 11 months)
Note that backup retention also depends on your schedule.
The schedules available to you depend on your tier.
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.
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:
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 within the region your project is hosted in. This means that in the rare event a data center becomes unavailable, your backups are still available.