Ask most business owners whether their website is backed up, and they’ll say yes. Ask when they last restored one, and the room goes quiet. Backups are like insurance: you only find out whether they work on the day you need them. Unlike insurance, though, you can test them in advance, and almost nobody does.
Why backups matter more than you think
Your website can be lost or damaged in many ordinary ways:
- A plugin or WordPress update goes wrong and breaks the site.
- Someone deletes the wrong page or overwrites important content.
- The site is hacked and files or the database are altered.
- The hosting company has a failure, or your account is suspended.
- A developer makes a change that can’t easily be undone.
In every case, a recent, clean, working backup turns a crisis into an inconvenience. Without one, you may be paying to rebuild from memory and old screenshots.
What a good backup actually includes
A WordPress site has two main parts, and a backup needs both:
- The files: WordPress itself, your theme, your plugins and everything you’ve uploaded, such as images and documents.
- The database: your pages, posts, settings, users, form entries and orders.
A backup of only one half is often useless. A surprising number of “backups” turn out to be missing the uploads folder or the database.
The rules of a backup you can trust
Automatic
Backups that depend on someone remembering will eventually be forgotten. They should run on a schedule, daily for most business sites and more often if content or orders change constantly.
Off-site
A backup stored on the same server as your website can disappear in the same incident. At least one copy should live somewhere separate: a different provider, a different region, a separate storage service.
Kept long enough
Some problems, especially hacks, go unnoticed for weeks. If you only keep the last three days of backups, you may only have three days of infected copies. Keeping a longer history, such as daily backups for a few weeks plus older monthly ones, means you can go back before the problem started.
Protected
Backups contain everything about your site, sometimes including customer information. They should be stored securely, with access limited to people who need it.
Tested
This is the step that’s almost always missed. A test restore means actually rebuilding the site from a backup, usually on a private staging copy, and checking it works: pages load, images appear, forms submit, you can log in. Do this regularly, and after any major change to how backups are made.
“But my host does backups”
Many hosts do, and that’s a good start. But it’s worth checking:
- How often do they run, and how long are they kept?
- Are they stored separately from your server?
- Can you restore them yourself, or only by asking support?
- Is restoring included, or does it cost extra?
- Do they cover both files and database?
Some hosting backups exist mainly to protect the host, not you, and come with limits you’ll only discover in an emergency. A second, independent backup is cheap insurance on your insurance.
How much is your website worth to rebuild?
A useful exercise: imagine your site vanished today with no backup. What would it cost to rebuild? Think about design and development, every page of content, product listings, blog posts, form entries and the time your team would spend. Then think about the enquiries lost while it’s down.
For most businesses, that figure is many times what a proper backup routine costs each year.
Restoring under pressure
When something goes wrong, restoring isn’t just pressing a button. Someone has to decide which backup to use, often the most recent one taken before the problem started, which may not be the newest. They need to restore files and database together, check for anything that changed since (new orders or form entries, for example) and confirm the restored site works before telling anyone it’s fixed.
That’s why a written restore plan, with who does what and where everything lives, is worth as much as the backups themselves. In a stressful moment, nobody should be working it out from scratch.
A simple backup checklist
If you can’t tick every box, your backup plan has a gap.
Backups and hacks: keep one copy out of reach
If someone gains control of your website or hosting account, backups stored inside that same account may be deleted or tampered with too. That’s why at least one backup copy should be held with a separate provider, under separate logins, ideally with protection against deletion for a set period. It’s a small step that keeps a bad day from becoming a catastrophe, and it’s one of the first things we check when reviewing how a site is protected.
The takeaway
Backups are the cheapest insurance your website will ever have, but only if they’re complete, stored separately, kept long enough and tested. The test is the part that turns a backup from a hope into a plan.
Backups you can rely on are a core part of our monthly maintenance plans, so on the day you need one, it works. If you need a restore right now, contact us and we’ll prioritize it.