Snapshots
Every environment is snapshotted daily by default, or as often as hourly. Snapshots are incremental, so only what changed is copied, and each is kept for 30 days.
Snapshots, step by step
-
1
Daily, without asking
Scheduled snapshots are on for production from day one, daily by default and as often as hourly. Each covers files and database but copies only what changed, so they are quick and light.
-
2
Take one before a change
Press Take snapshot and add a note, like the update you are about to run. It takes about a minute and the site stays online.
-
3
Choose what to restore
Restore everything, only the database or only the files. Type the domain to confirm, so nothing is restored by mistake.
-
4
A safety copy comes first
The site as it is now is snapshotted before the restore starts. The site is offline for a few minutes, then back.
Questions about snapshots
Daily by default, as often as hourly, and each one is kept for 30 days. Snapshots are incremental, so only changed files are copied. You can change the schedule for a whole cluster or for one environment. You can also take a one-off snapshot whenever you need one.
Yes, for a few minutes while the data is copied back. A snapshot of the site as it is now is taken first, so you can undo the restore if it is not what you wanted.
Each package includes a snapshot quota of twice its storage. When snapshots fill it, the oldest unprotected ones are deleted first. A site’s newest snapshot is always kept.
See snapshots on your own cluster
Tell us how many sites you run and on what. An engineer sizes a cluster with you and shows you the panel on a live one.