Website backups that actually restore: a plan for a small business
Most small business owners believe their website is backed up. Often it is, in the sense that a copy of something exists somewhere. What they find out on the bad day is whether that copy can be turned back into a working site, store and inbox, and how long that takes. A backup you have never restored is a hope, not a plan.
This guide covers what a small business site really needs copied, where the copies should live, how often to make them, and the test that tells you whether any of it works.
What can go wrong
Sites are lost in ordinary ways far more often than dramatic ones. An update to a plugin or theme breaks the layout and the old version is gone. Someone deletes a page, a product or a folder by mistake. A hosting account is suspended over a billing problem, or the host itself closes. An attacker gets in through an old plugin, changes files and adds spam pages, and by the time anyone notices, the recent backups contain the same damage. Each of these needs a slightly different kind of copy, which is why one backup is rarely enough.
1. Know what makes up your site
A website is usually several things kept in different places. Write them down before you plan any backup:
- Files: the pages, theme, plugins, images and uploads.
- The database: on most content systems and stores, the posts, products, orders, customers and settings live here, not in the files.
- Configuration: domain and DNS settings, email routing, redirects, and the settings inside your hosting control panel.
- Outside services: your payment provider, email marketing list, booking system or forms service each keep their own data.
- Access: who holds the logins for the domain registrar, the host and each service, and where the recovery codes are kept.
A backup of the files alone restores a site with no products, no orders and no posts. A backup of everything except the domain account leaves you unable to point the restored site anywhere.
2. Make copies that do not depend on the host
Many hosts include automatic backups, and they are worth having for a quick undo. But a backup kept by the same company, in the same account, disappears with that account. Keep at least one copy somewhere the host cannot reach: your own cloud storage, a second provider, or a drive you control. A widely used rule of thumb is three copies, on two different kinds of storage, with one kept away from the others. For a small site that can be as simple as the host's daily backup, a weekly export to your own cloud storage, and a monthly copy on a drive kept offline.
The separate copy matters most against ransomware and account takeovers: anything an attacker can reach with your login, they can delete.
3. Match how often you copy to how much you can lose
Ask one question for each part of the site: if this broke right now, how much recent work could we afford to redo? A brochure site that changes twice a year can be copied after each change. A store that takes orders every hour needs its database copied at least daily, because orders placed since the last copy are the hardest thing to recreate. Keep older copies as well as the newest. If damage goes unnoticed for two weeks, a backup set that only holds the last seven days holds nothing useful.
4. Do not forget email and the domain
If your email runs through a hosted service, the mailboxes are usually safer than the website, but the domain settings that deliver the mail are not backed up anywhere by default. Export or screenshot your DNS records, including the mail records, after every change, and keep that copy with your other backups. Set the domain to renew automatically on a payment method that will not expire unnoticed, and make sure more than one trusted person can reach the registrar account. A lapsed domain takes the website and the email down together.
5. Protect the backups themselves
A backup is a full copy of your business data, often including customer names, addresses and order history. Treat it like the original:
- Store it encrypted where the service allows it, and never in a shared folder with a public link.
- Keep the passwords and keys for the backup somewhere other than the system being backed up.
- Delete old copies on a schedule instead of keeping everything forever. Data you no longer need is data you can no longer lose.
6. The test restore
This is the step almost everyone skips, and the only one that proves the rest. At least twice a year, and after any big change to the site:
- Restore to a separate place, never over the live site: a staging copy, a test subdomain or a local machine.
- Time it. Note how long it took from deciding to restore until the copy worked. That number is your real recovery time.
- Walk the copy like a customer. Open the main pages, search, log in, and check that recent orders, posts and images are there.
- Write down every step you had to look up or guess, and fix the notes. The next restore may be done in a hurry, by someone else.
Mistakes we see most
- Backing up the files but not the database, so the restored store has no products or orders.
- Keeping every copy inside the hosting account, so one suspension or break-in removes them all.
- Keeping only a few days of copies, so damage found late has already replaced every clean backup.
- A backup job that stopped months ago without anyone noticing. Check that the newest copy is recent, not only that the job exists.
- Restoring straight over the live site without checking the copy first, which turns one problem into two.
The short version
List every part of your site, including the database, the domain and your outside services. Keep at least one copy away from your host, copy as often as you can afford to lose work, and keep enough history to go back past damage that is slow to notice. Protect the backups like the data they hold. Then restore one to a test location, time it, check it the way a customer would, and write down what you learned.