Recommended backup plans: example sets of backup jobs

For server administrators · Updated 2026-10-29

On this page
  1. Plan 1: a small server (the basic, safe plan)
  2. Plan 2: online shops and busy websites
  3. Plan 3: many accounts, different packages
  4. How to choose
  5. Common questions

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)

JobWhat to copyWhenCopies to keepDestination
Nightly on serverFiles, Databases, EmailDaily at 02:0014This server (incremental)
Weekly off serverFiles, Databases, EmailWeekly, Sunday at 04:008External destination

Two weeks of daily restore points on the server, two months of weekly copies elsewhere.

Plan 2: online shops and busy websites

JobWhat to copyWhenCopies to keepDestination
Databases every 15 minutesDatabasesEvery 15 minutes96This server (incremental)
Files every 6 hoursFiles, EmailEvery 6 hours28This server (incremental)
Nightly off serverFiles, Databases, EmailDaily at 03:0014External 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

JobAccountsWhenCopies to keepDestination
Premium hourlyAccounts of these packages: your premium packagesEvery hour48This server (incremental)
Everyone nightlyAll accountsDaily at 01:307This server (incremental)
Everyone weekly off serverAll accountsWeekly at 05:004External destination
Monthly archiveAll accountsMonthly on day 1 at 06:006A 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.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.