Who actually backs up your site?

Ask a hosting provider if your site is backed up and you'll almost always hear yes. "Daily backups" is on nearly every plan. So most owners file the question away as solved and never think about it again — until the day something breaks, they go to restore, and discover what that phrase actually promised. Which, very often, is nothing they can hold anyone to.

Here's the distinction the word "backup" hides, and it's the whole piece: there's an enormous difference between a backup offered as a convenience and one offered as a guarantee. Almost all hosting backups are the first kind. The contracts say so, in language you were never meant to read.

Read a typical hosting agreement and you'll find some version of the same sentence: the customer is responsible for maintaining their own backups. The host provides backups "as a convenience, not as a guarantee against data loss." That's not a scam — it's standard, and it's even reasonable. But it means the reassuring "daily backups" on the sales page and the actual liability in the contract are pointing in opposite directions.

"Daily backups" tells you a copy might be made. It says nothing about whether you can ever get it back. A backup nobody has restored is a guess wearing the costume of a safety net.

Why this turns into disasters

The gap stays invisible right up until it's catastrophic, and the failures are mundane, not exotic:

• The backup that was never tested. It ran every night for two years. The first time anyone tried to restore it — the day it mattered — it was corrupt, or incomplete, or covered the wrong files.
• The backup in the same place as the site. If your only copy lives on the same server (or in the same data centre) as the live site, a single failure takes both. In 2021 a fire destroyed an entire data centre of a major host; for some sites, data that lived only there was gone permanently.
• The retention you didn't read. "We keep backups" can mean "for the last 7 days." Discover a problem on day 8 — a slow database corruption, a quiet hack — and the clean version is already overwritten.
• The cheaper the plan, the likelier none of this is covered at all — and even premium hosting doesn't guarantee a working restore.

What actually protects you

The principle is older than the cloud and it's one line: your data isn't safe until a copy exists somewhere you control, and you've proven you can bring it back. The plain shape of that is the long-standing 3-2-1 rule.

Notice the through-line to everything else on this site: the safest backup is the one you hold, separate from any single provider. It's the same sovereignty that makes an owned, portable site stronger than a rented one. A copy you control is a copy no host's bad day, price hike, or shutdown can take from you.

The questions that reveal the real answer

Don't ask "do you do backups?" — the answer is always yes. Ask past it:

1. Are backups a guarantee or a convenience in the contract — and who's liable if a restore fails?
2. How do I actually restore one, and has that restore ever been tested?
3. How far back do they go, and how quickly would a problem have to be caught?
4. Are backups stored separately from the live server, or in the same place that could fail with it?
5. Do I have my own copy — one I control, that survives leaving this host entirely?

If you have a tested restore, off-site, in your own hands, you're genuinely safe — the host's backups are a bonus, not your only hope. If the honest answers are "convenience, untested, same server, seven days," that's not a disaster yet. It's the warning that arrives in time — which is the only kind worth having.