Most business owners only think about website backups on the day they need one: after a hack, a failed update or an accidental deletion. That is the worst moment to discover the last backup is six months old, stored on the same server that just failed, or missing the database.
Backups are not glamorous, but they are the cheapest insurance a website has. This guide explains what a complete backup contains, how often to make one, where to keep it and how to be sure it will actually work.
The short answer
A useful website backup:
- includes everything needed to rebuild the site: files, database and configuration;
- runs automatically on a schedule that matches how often the site changes;
- is stored in more than one place, with at least one copy away from your hosting server;
- is kept for a period of time, so you can go back to a version from before a problem started;
- has been tested, so you know a restore works and how long it takes.
What a complete website backup includes
For a typical WordPress site, a backup has two main parts:
| Part | What it contains | Why it matters |
|---|---|---|
| Files | Themes, plugins, uploaded images and documents, core files | Without them the site has no design, features or media |
| Database | Pages, posts, settings, users, form entries, products | Without it the site has no content |
| Configuration | Server settings, redirects, environment settings | Without it a restored site may not run correctly |
Many “backups” only capture one part. A copy of the files without the database restores an empty site. A database without the uploads folder restores pages with missing images. WordPress’s own guide to backing up a site covers both parts.
Also keep a record of things outside the server: domain registrar details, DNS settings and email configuration. They aren’t part of a website backup, but rebuilding them from memory during an outage is slow.
How often should you back up?
Match the schedule to how often your site changes and how much you could afford to lose.
- Brochure sites that change a few times a month: a weekly backup, plus one before any change.
- Sites with regular content or form submissions: daily backups, so you never lose more than a day.
- Sites with frequent transactions or bookings: more frequent database backups, sometimes several a day.
Whatever the schedule, always take a fresh backup before updates, redesigns, plugin changes or moving host. Those are the moments when things most often go wrong. Our website maintenance checklist builds this into a monthly routine.
It also helps to think about the question from the other direction. Ask how much work you would be willing to redo if the site failed right now: a week of blog posts, a day of enquiries, an hour of bookings. That amount sets your backup frequency. Then ask how long the site could be offline before it hurt the business. That sets how quickly you need to be able to restore, and whether a simple download is enough or you need a faster, rehearsed process.
Where to keep backups
A backup stored only on the same server as your website protects against small mistakes, but not against the server failing, being compromised or the hosting account being closed.
A common rule of thumb is 3-2-1: three copies of your data, on two different types of storage, with one copy off-site. For a website, that usually means:
- the live site itself;
- backups kept by your hosting provider;
- a separate copy stored with a different provider, such as cloud storage in another account.
Keep access to off-site backups separate from your website login, so an attacker who gets into the site cannot delete the backups too.
How long to keep backups
Problems are not always noticed immediately. Malware can sit quietly for weeks, and a page deleted by mistake may not be missed for a month. Keep enough history to go back before the problem started, for example daily backups for a few weeks and weekly or monthly copies for longer. Balance retention against storage costs and any data protection obligations for personal data stored in form entries.
Test your restore
A backup you have never restored is a hope, not a plan. At least a few times a year:
- restore a recent backup to a staging site or a temporary location, never over the live site;
- check that pages, images, forms and logins work;
- note how long the restore took and any steps that were unclear;
- write those steps down so anyone can follow them in an emergency.
Testing often reveals missing pieces, such as an uploads folder excluded to save space or a database export that is incomplete.
Common backup mistakes
- Relying on the host alone. Host backups are useful, but check how often they run, how long they are kept and whether you can restore them yourself.
- Backups on the same server. If the server fails, the backups fail with it.
- Plugins that time out. On large sites, some backup plugins quietly fail part-way. Check the logs and the file sizes.
- Never checking notifications. Failed backup emails go unread for months.
- No backup before changes. Updates are the most common reason a restore is needed.
- Keeping only the latest copy. If the latest copy already includes malware, you need an older one.
Backups and security
Backups don’t prevent attacks, but they make recovery possible. Combine them with the basics: regular updates, strong unique passwords, two-factor authentication and security monitoring. Our WordPress security guide covers these in more detail.
If a site is hacked, restoring a backup is often only part of the fix. You also need to close the hole that let the attacker in, or the problem returns.
Frequently asked questions
Are hosting backups enough?
They are a good first layer, but not enough on their own. Keep at least one copy with a different provider, and check that you can download or restore the host’s backups when you need them.
Do backups slow down my website?
A well-configured backup runs at quiet times and has little effect. Backups that run during busy hours on a small hosting plan can slow the site briefly, so schedule them for off-peak times.
Can I back up a website myself?
Yes. Many hosts offer one-click backups, and backup plugins can send copies to cloud storage. The hard part is not making the first backup but making sure it keeps running, stays complete and is tested.
What to do next
This week, find out three things: when your last backup ran, where it is stored, and whether anyone has ever restored it. If any answer is “not sure”, that is your first task.
Our website maintenance care plans include regular backups alongside updates and monitoring, and daily off-site backups are available as an add-on for an extra fee. If you are planning a new site, our website design and development service sets up backups before launch.