A website backup strategy that actually works
Web hosting · CMS development · Contact
Short answer: Keep a full backup of your site files and database, store at least one copy away from the main server, and test a restore at least once a year. A backup you have never restored is a hope, not a plan.
What to back up
- Files. Themes, uploads, custom code and configuration.
- Database. Your content, orders, enquiries and customer records.
- Settings. Any configuration not stored in files, such as email settings.
How often
- Database: daily for sites that take enquiries or orders.
- Files: weekly, or after any significant change.
- Before every update to the website software or plugins.
Where to store copies
Keep at least one copy somewhere other than the main hosting account. A second hosting account, a cloud storage folder or an offline drive all work. Make sure the copy is protected with a password and access is limited.
Test a restore
- Restore the most recent backup to a test copy of the site.
- Check the homepage, one inner page, a form and the admin login.
- Note how long it took and what needed fixing.
- Write the steps down so someone else can follow them.
Common mistakes
- Relying on the host's backup without knowing the restore process.
- Storing backups only on the same server as the site.
- Keeping backups for one day only, so a problem noticed later has no clean copy.
- Never checking that backups still run.
Frequently asked questions
How many backups should I keep?
A common approach is daily copies for a week, weekly copies for a month and monthly copies for a year.
Does a backup protect against hacking?
It helps you recover, but it does not stop an attack. Keep software updated and use strong logins as well.
Who should own backups?
The business should know where they are and who can restore them, even if a developer does the work.
Related reading
Ready to build something great?
Tell us about your project. We reply within one working day.
Start a project