Website backups: what good looks like and how to test them
A good backup is automatic, stored away from the server, covers files and database, keeps weeks of versions and has been restored once. How to check yours.
By Sohail Hussain21 November 20265 min read
A good website backup is automatic, contains everything needed to rebuild the site (files, database and configuration), is stored somewhere other than the server it protects, keeps several weeks of versions, and has been restored successfully at least once in the last few months. If any one of those is missing, the backup is weaker than it looks. A backup that has never been restored is a hope, not a backup.
Most businesses believe they have backups because a host's plan mentions them. Few have checked what is in them, where they are kept, or how long a restore takes. Backups with tested restores are part of every plan in our website care and maintenance service, with the off-site copy held in storage the client owns. This guide covers what to check, by platform, with a short test you can run yourself.
What needs backing up?
It depends on the platform, because each one keeps its data in different places.
| Platform | What to back up | Who usually does it | What people forget |
|---|---|---|---|
| WordPress | Database, wp-content (uploads, themes, plugins) and wp-config.php | A backup plugin or the host | The database: a files-only backup restores an empty site |
| Next.js or static site | Code in a Git repository; content in the CMS; media storage; environment variables | Git and the CMS provider | Environment variables and API keys, which are not in the repository |
| Shopify, Wix, Squarespace | Products, customers, orders, pages and theme code, through exports or a backup app | Partly the platform | The platform protects against its own failures, not against you deleting something |
| Web app or portal | Database with point-in-time recovery, uploaded files, secrets | The developer, through the cloud provider | Uploaded files stored outside the database |
Two things are not part of a website backup at all. Business email lives with Google Workspace or Microsoft 365, and the domain and DNS records live with the registrar and DNS host. Keep an export of your DNS records alongside the site backup; it is the fastest way to rebuild after an account problem.
How often should you back up, and for how long?
Match the frequency to how often the site changes, and the retention to how long problems take to find.
Frequency. A brochure site that changes once a month is fine with weekly backups. A site that stores form submissions, bookings or orders needs daily backups at least, because every day lost is customer data lost. A web app needs continuous or hourly database backups, which most managed databases offer as point-in-time recovery.
Retention. Keep at least 30 days of regular backups, plus a monthly copy for six to twelve months. Hacks are often discovered weeks after they start, and a backup from last night may already contain the problem. A WordPress site that was quietly injected with spam links a month ago needs a copy from five weeks ago.
Before every change. Take a manual backup before any update, plugin install or migration, whatever the schedule says.
Where should backups be stored?
Somewhere the thing that breaks the site cannot reach. The old rule of thumb is three copies, on two different kinds of storage, with one off-site. For a website, that translates to:
- The live site itself.
- The host's own backups, which are convenient for quick restores.
- An off-site copy in a separate account, such as cloud storage your company owns, that the host and the site's admin logins cannot delete.
The third copy is the one that matters. If the hosting account is suspended, the host has an outage, or an attacker gets an admin login, backups stored on the same server or in the same account can disappear with everything else. Store the off-site copy encrypted, and limit who can delete from it.
How do you test a restore?
Restore to a copy of the site, never over the live one. A staging site is the right place.
- Pick a backup from at least a week ago, not last night's.
- Restore it to a staging site or a fresh local environment, following the steps you would use in an emergency.
- Check that pages load, images appear, logins work, and the last content change before the backup date is present.
- Time the whole process from start to a working site.
- Write down the steps, the time taken and anything that went wrong.
Do this quarterly, and after any change to hosting or the backup tool. The written steps matter as much as the test: a restore is usually needed at a bad moment, by someone who did not set up the backups.
The WordPress documentation on backups covers the database and file side in detail for that platform, and WordPress backup covers the plugins and settings we use.
What do backups cost?
Very little for a typical company site, as of October 2026:
- Backup plugins for WordPress: free versions exist; paid versions with off-site storage and scheduling cost roughly $0 to $100 a year.
- Off-site storage: a few gigabytes in a cloud storage bucket costs a few dollars a month at most, often less than one.
- Host backup add-ons: some hosts include daily backups; others charge a few dollars a month.
- Managed database backups for web apps: usually included in the database plan, with longer retention at extra cost.
If you run your own backup scripts on a server, the cron expression generator helps you set and check the schedule. The real cost is the quarterly restore test, which takes an hour or two of someone's time. That hour is what separates a backup from a hope.
When are backups not worth paying extra for?
When the platform already covers the risk. A static Next.js site with its code in a Git repository and its content in a hosted CMS has two copies of everything by default. An occasional CMS export and a note of the environment variables is all it needs; a premium backup service adds nothing.
Daily backups for a site that changes monthly are also money for nothing. Weekly is enough, as long as a restore has been tested. How much does website maintenance cost covers which line items in a care plan are worth questioning.
Where backups are not optional is self-hosted WordPress, any site that stores customer data, and anything you would struggle to rebuild from memory. For those, start today: turn on scheduled backups, add an off-site copy, and book the first restore test. If the worst happens, your website got hacked: a recovery plan shows where the backup fits, and the website maintenance guide puts the routine in context.
Was this guide useful?