Backup scheduling
Backup schedules and retention, site by site
An online shop’s database changes every hour, its images almost never. One daily backup of everything serves neither well.
The problem
One rule for every site isn’t enough.
Some sites need the database every night and a full backup every month. Others a full backup every week. With a single schedule you end up saving too much or too little.
And the “good” backup from before a big change shouldn’t disappear just because newer ones arrived.
How it works
Independent schedules, separate retention.
- 1
Create schedules
Up to five schedules per site: daily, weekly or monthly, at the hour you like in the site’s timezone.
- 2
Choose content and retention
Each schedule has its own content, like everything or database only, and how many backups to keep.
- 3
Keep forever
One click on a backup takes it out of retention: it will never be deleted automatically.
In detail
Typical setups.
- Full backup on the 1st of the month, keep 12
- Database only every night, keep 14
- Manual and pre-update backups with their own retention
- Schedules can be paused without losing their settings
- Storage shared by all the agency’s sites
FAQ
Frequently asked questions
What if two schedules are due at the same time?
They run one after the other: each site runs one backup at a time.
Does a backup kept forever use storage?
Yes, it counts towards your plan’s storage until you delete or release it.
Related features
Goes well with
Try it on your clients’ sites.
During the beta we welcome agencies in small groups and set up the first sites together.