Choosing a Backup Schedule
What You Need Before You Start
This guide shows you how to choose a website backup schedule that fits how often your site changes. It is for owners of blogs, brochure sites and online shops who want to know how often a copy is needed. Before you start, list what changes on your site each day, such as posts, orders or customer accounts, and check your current backup settings.
Steps to Set Your Backup Schedule
- Measure how much your site changes. Note which content and data change, such as new posts, orders, comments and customer accounts, and how often each one changes. A site that changes daily needs more frequent copies than one that changes a few times a year.
- Decide how much work you can lose. Estimate how many hours or days of work you could rebuild after a failure. That gap sets the longest acceptable time between copies, a limit explained in RPO vs RTO.
- Pick a starting schedule for your site type. A brochure site may need a copy after each edit plus a weekly copy. A blog or news site often suits daily copies. An online shop or membership site commonly needs daily copies at minimum, and more often when activity is high.
- Turn on the schedule and confirm it runs. Use automatic scheduling where your host or backup tool offers it, as described in automatic vs manual backups. Check the log after the first few runs to confirm that each copy completes.
- Review the schedule as the site changes. A new product line, a sales event or a jump in traffic may mean the gap between copies should shrink.
Common Mistakes and When to Ask for Help
- Copying someone else's schedule. A weekly copy can be right for one site and far too slow for another.
- Overwriting one copy. If each run replaces the last, a problem noticed late can destroy every good copy. Keep several dated copies.
- Never testing a restore. A backup that has never been restored is unproven, so test a restore from time to time.
Ask your host's support team if scheduled backups are not offered, if they fail repeatedly, or if you need copies taken more often than your plan allows.
Is a daily backup always necessary?
Not always. A site that changes only a few times a year may need a copy after each change rather than every day. Daily copies make sense when the site changes every day or when losing a day of data would be costly. Set the schedule based on the cost of losing that work.
How long should I keep old backups?
Keep enough history to cover the time it might take to notice a problem. If a hack or a corrupted database could go unnoticed for several weeks, keeping only the last few days is risky. The full approach is described in backup retention policy.
What should I do if a backup fails?
Check the log for the error, fix its cause and run a manual backup as soon as possible. Repeated failures usually point to limited disk space, wrong permissions or a backup too large for its time window. Ask your host's support if you cannot find the cause, because until a copy succeeds, your last good copy is your only protection.