Backup schedule
How often an environment is backed up, when the next backup is due and when each backup expires.
On this page
Scheduled backups run on their own, as often as the package sets. The Backups section of a site shows the schedule of the environment chosen in the site header.
What the card shows
| On the card | Meaning |
|---|---|
| Scheduled backups | On with how often, or Off. The line below reads Set by the site's package or Set by the cluster's package. |
| Next scheduled | When the next scheduled backup is due. |
| Latest backup | When the last backup was taken, and its type. |
| Stored | The space this environment's backups use, and how many are kept. |
How often backups run
The package sets one of: every hour, every 2, 3, 4, 6 or 12 hours, daily, weekly or monthly. Daily backups run shortly after 02:00 UK time, weekly ones on Sunday and monthly ones on the 1st.
A staging environment starts with scheduled backups off. To turn them on or off for one environment, see Backups.
One-off backups can be taken whatever the schedule, up to 20 an hour for each site. For the schedule of a whole CoreCluster, see Cluster backups.
How long backups are kept
Each backup shows when it will be deleted under Expires; the package sets how long that is. A backup you keep reads Kept and has no expiry.
When the backup space is full, the oldest backups that are not kept are deleted early. The newest backup of each site is never deleted this way.
If a scheduled backup fails
It is tried up to 3 times. If it still fails, Backups says so and gives the time the next one is due.