The CW Corner – What Website Backups Actually Cover (and What They Don’t)
Website backups sound reassuring, but “we have backups” answers a question nobody finished asking. What gets copied? Where does it live? And could it actually restore your site?
Those details are the fine print. Knowing them can help you understand what a backup protects, what it leaves out, and what to ask your host or developer.
What a typical WordPress backup contains
A typical WordPress backup has two parts: the database and the website files. You need both to restore a complete site. WordPress explains the two-part backup in its documentation.
The database: what your site says
The database holds much of your site’s changing information. That includes posts, pages, users, settings, plugin configuration, and comments.
Think of your site as a house. The database is what’s written on the walls: the words, arrangements, and instructions that make the place yours.
The files: what your site uses
The files include WordPress itself, themes, plugins, and uploaded images and documents. Depending on your setup, they may also include other site code and related files.
In the house analogy, the files are the furniture and pictures. They give your content its look and provide the tools that make features work.
Neither half alone gives you your whole site back. Files without the database may leave you with an empty framework. A database without the files may have words and settings, but not the right images, design, or working features.
Ask whether your backups include both parts, saved together as a usable set. The WordPress backup guide explains why files and database data need separate attention.
Where the backup lives matters
A backup copy stored on the same server as your website may disappear with that server. If the server fails or becomes inaccessible, both the site and its nearby copy could be affected.
An off-server copy is stored somewhere separate from the website’s own server. In plain terms, it’s another copy kept elsewhere, rather than a spare tucked beside the original.
Access matters, too. If the backup folder is available through the same account used to administer your site, an intruder with that access might delete or encrypt the copies. That makes the backups less useful when you need them most.
Ask who can reach the copies and how they’re protected. At The CharlesWorks Corner, our arrangement keeps copies on separate servers that site administrators cannot reach. That’s one example of an important detail to understand.
For more background on hosting settings, see what your hosting control panel actually does.
What website backups do not cover
A website backup is not a complete copy of your business or everything connected to your online presence. Here are a few things it may not include:
- Your domain registration. A restored website does not renew or recover the name customers use to find you. See what happens when your domain expires.
- Business email messages. If your mailbox lives outside your website hosting account, website backups may not include its messages.
- Third-party accounts and analytics history. Accounts with outside services, saved reports, or past tracking data may live elsewhere. A site copy may not restore them.
- Tracking setup. Website code or settings that connect a tracking service might be included, but the third-party account and its history are separate questions.
- Social profiles. Your business’s social media pages and their content are not part of a website backup.
- Search rankings, reviews, and reputation. A restore does not bring back lost visibility, customer reviews, or confidence.
- Time and trust. Backups cannot give back the hours spent fixing a partly broken site or the customer trust affected while it was unavailable.
There’s another subtle limitation: a backup cannot contain changes made after that copy was created. If a problem went unnoticed for a while, it may already exist in every copy still available.
And restoring a clean copy does not explain what caused the break. If the cause remains, the same problem may return. A restore can help recover the site, but the underlying issue still needs attention.
Our older note on nightly website backups discusses backup timing. This article focuses on what those copies cover.
Questions to ask your host or developer
Ask for clear answers to these questions. Write them down so you can find them later.
- What gets backed up? Does the copy include both the database and files, or only one?
- How often are copies made? Ask what schedule applies to your particular site.
- How long are copies kept? How far back can you reach?
- How does a restore work? Who performs it, and does it cost extra?
- Where do the copies physically live? Are they stored away from your website’s server?
A vague answer to any of these questions is worth chasing. “It’s backed up” may sound comforting, but you deserve to know what that means in practice.
Why the retention window matters
Retention means how long your provider keeps backup copies before removing or replacing them. That window determines how far back you may be able to go.
If a problem is discovered late, you may need a copy older than the window holds. In that case, every available copy could already include the unwanted change or the hidden problem.
Ask how many days your provider keeps copies, and whether you can access older ones. Don’t assume a particular window without checking.
Test a restore before you need one
A backup that has never been restored is a hope, not a plan. A completed backup job does not, by itself, prove that the copy can rebuild your site.
Ask your host or developer to restore a copy into a separate folder or staging site. A staging site is a private version used for testing, away from your live website.
Check that key pages, images, and features appear as expected. For a site with forms or other important functions, ask how those can be checked safely.
Do this once in a while, not during a crisis. A successful test gives you practical confidence and may reveal gaps while there’s time to address them.
Take a fresh copy before important changes
Some routine changes can create problems, even when they’re sensible. Make sure a fresh backup is available just before a plugin or theme update, adding a new form, giving someone administrator access, or making a major content edit.
You don’t need to turn every small adjustment into a technical production. Just build a quick backup check into the changes that could affect important parts of your site.
Our guide to a website maintenance routine you will actually keep can help you make that check part of regular care.
Keep a simple website inventory
Create a one-page inventory with the basics: where your site is hosted, who your domain registrar is, what backup arrangement is in place, and who to call for help.
Keep a copy offline and share it with one other trusted person. If something goes wrong, your business won’t depend on one person remembering every provider, login, or arrangement.
If you need help understanding your hosting or backup setup, ask your host or developer to walk you through it. There’s no need to know every technical detail. A clear answer about what’s covered is a very good place to start.
European Union General Data Protection Regulation Compliant