«The hosting surely has backups» is a phrase you hear regularly, usually right after something has already gone wrong. In practice, most hosting plans either have no automatic backups at all, or they keep a copy from the last day or two and overwrite it daily — meaning if the problem wasn't caught right away, there's nothing left to restore. Let's break down where this misconception comes from and what happens when it doesn't hold up in practice.

Where the illusion comes from

A site runs for months and years without a single failure, and gradually the feeling sets in that it'll always be this way — why pay for backups of something that's already running stably. The logic is understandable, but it confuses «nothing has broken so far» with «nothing will break» — these are two different statements, and the second one doesn't follow from the first at all.

What can actually go wrong

• A failed plugin or module update that takes the whole site down.
• A hack — not necessarily targeted, more often automated, through a known vulnerability in an outdated CMS version.
• Human error: the wrong file got deleted, a rollback went to the wrong place, a database got overwritten during a migration.
• A failure on the hosting provider's side — rare, but it happens, and the hosting's liability for the client's data is usually spelled out in the contract far more modestly than it seems.

In every one of these cases, the question is the same: is there a working copy of the site made before the problem occurred, and can it actually be restored. Without a configured backup process, the answer is no — and you can only find that out once it's already too late.

How it should be set up

Regularity — copies should be made on a schedule, not on a whim, and at a frequency that matches how often the site actually changes. Storage separate from the server — a copy sitting in the same place as the site itself won't help if the server fails or gets hacked entirely. Restore testing — a backup that's never once been test-restored is theory, not a guarantee; it's worth checking every so often, not only at the moment of a real disaster.

What to do right now

There's no need to wait for a convenient moment to sort this out — it's worth simply confirming one fact: when the last working backup of your site was made, and whether you know how to restore it if needed. If there's no answer to that question — that in itself is already the answer to whether backups need to be set up.

If you're not sure whether your site has working backups or how often they're made — tell us about it through the «Discuss a Task» form, we'll check the current situation and set up regular backups so this question stops being a lottery.

« Back to blog