Recommended backup plans: example sets of backup jobs
On this page
A good plan has short-interval copies on the server for quick restores, and longer-interval copies off the server in case the server itself is lost. Below are job sets you can create in Backup Jobs (section Websites). See how to create a backup job for the form.
Plan 1: a small server (the basic, safe plan)
| Job | What to copy | When | Copies to keep | Destination |
|---|---|---|---|---|
| Nightly on server | Files, Databases, Email | Daily at 02:00 | 14 | This server (incremental) |
| Weekly off server | Files, Databases, Email | Weekly, Sunday at 04:00 | 8 | External destination |
Two weeks of daily restore points on the server, two months of weekly copies elsewhere.
Plan 2: online shops and busy websites
| Job | What to copy | When | Copies to keep | Destination |
|---|---|---|---|---|
| Databases every 15 minutes | Databases | Every 15 minutes | 96 | This server (incremental) |
| Files every 6 hours | Files, Email | Every 6 hours | 28 | This server (incremental) |
| Nightly off server | Files, Databases, Email | Daily at 03:00 | 14 | External destination |
Orders and form entries are never more than 15 minutes old in a copy. Limit the 15-minute job to the shop accounts with Only these accounts or Accounts of these packages if other accounts don't need it.
Plan 3: many accounts, different packages
| Job | Accounts | When | Copies to keep | Destination |
|---|---|---|---|---|
| Premium hourly | Accounts of these packages: your premium packages | Every hour | 48 | This server (incremental) |
| Everyone nightly | All accounts | Daily at 01:30 | 7 | This server (incremental) |
| Everyone weekly off server | All accounts | Weekly at 05:00 | 4 | External destination |
| Monthly archive | All accounts | Monthly on day 1 at 06:00 | 6 | A second external destination |
How to choose
- How much work could you lose? That is your interval. A blog changes daily; a shop changes every minute.
- How far back may you need to go? Interval × copies. Problems like a hacked site are often found days later, so keep at least a week of copies.
- Keep one job off the server. Copies on the server do not help if the server is lost.
- Spread start times so heavy jobs do not run at the same moment. Short intervals follow the clock (:00, :15, :30, :45).
- Watch databases: each database copy takes its full compressed size. See how backups use disk space.
- To an external destination, prefer daily or longer for files: each run sends a full archive of each account.
Common questions
Do suspended accounts get backed up?
Only when Include suspended accounts is ticked in the job.
Can a customer have a different plan than the others?
Yes. Use Only these accounts or Accounts of these packages in a job made for them, and All accounts except these in the general job if they should not be copied twice.
Should I test my backups?
Yes. Restore a file or a database from each job now and then, into a new folder, to be sure the copies are what you expect.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to create a backup job (schedule automatic backups)
Schedule automatic backups of files, databases and email — from every 15 minutes to monthly — with how many copies to keep and where to store them.
- How backups use disk space (incremental snapshots explained)
Where backups are stored on the server, why incremental snapshots take little space, what databases cost per copy, and how to free backup disk space.
- How to add an external backup destination (off-server backups)
Keep backup copies off the server on S3-compatible storage, an SFTP or FTP server, Google Drive, OneDrive or Dropbox, then send a backup job there.
- Snapshots vs full backups: which backup type to use
The difference between incremental snapshots on the server and full backup archives: space, speed, restores, downloads and external storage.