Our website is in Dutch; support is available in English.

Backups and retention: what to ask your host

Backup versus snapshot, why one day of retention is not enough, and six questions for your host.

Updated 4 minute read

Contents of this article
  1. A snapshot is not a backup
  2. Retention: why one day is not enough
  3. Files and databases are two different things
  4. Questions to ask your host
  5. A backup that has never been restored is an assumption
  6. How we do it ourselves
  7. What we don't do here
  8. Further reading

Almost every host says they make backups. That tells you very little until you know where they are kept, how long they are kept, and whether anyone has ever restored one. This page covers the terms and the questions you can ask, whoever your host is.

A snapshot is not a backup

A snapshot is a point-in-time copy of a disk or virtual machine, usually stored on the same storage the machine itself runs on. It is useful: you can undo a failed update in a few minutes. But if that storage fails, the snapshot disappears along with the machine.

A backup is a copy that exists separately from the original, on different hardware and preferably in a different location. That is the difference: a snapshot protects you against a mistake, a backup protects you against loss.

So a backup that sits next to your data is not a backup. That also goes for the backup/ folder in your own web space and for a database dump left on the same server: ransomware encrypts those just as easily as everything else.

Retention: why one day is not enough

Retention is how long a backup is kept before a newer one overwrites it. With one day of retention you have exactly one version: yesterday's.

That goes wrong because damage rarely happens on the day you discover it. Ransomware often sits in an environment for days or weeks before it strikes, and a botched import or a corrupt table sometimes only shows up when someone looks for an old record. If you notice on day five, your backups have by then been overwritten five times with the broken state.

So don't ask whether there are backups. Ask how many versions you can get back, and how far back they go. Several daily versions, plus a weekly or monthly copy kept longer, is the pattern you are looking for.

Files and databases are two different things

A website consists of files and, for a CMS or web shop, a database. Restoring files is simple: it is copying. Restoring a database is different. It has to be consistent and captured at the same moment as the files, otherwise your CMS points to images that don't exist yet, or the other way round.

So also ask whether you can have only a database restored, or only one folder. Restoring an entire server is sometimes far too blunt an instrument for a problem the size of one table.

Questions to ask your host

  1. How often is a backup made? Daily is common. If you run a web shop, ask what you lose if something breaks at 17:00 and the backup ran at 03:00.
  2. Where is the backup kept? On the same server, in the same data centre, or somewhere separate? And in which country?
  3. How long is it kept? Ask for the number of versions and the oldest version you can still request.
  4. Can I restore it myself, or does it go through support? And if it goes through support: can that happen outside office hours, and what does it cost?
  5. Can I restore a single file or a single database? Or is all-or-nothing the only option?
  6. Has a test restore ever been done? This question tells you the most, and it is the one asked least often.

A backup that has never been restored is an assumption

When backup software reports "success", it means the writing succeeded. Not that the file is readable, not that the database is complete, and not that anyone knows the steps a restore takes. You only know that once you have actually done it.

So restore something once while there is no crisis. An old copy of your site in a test environment is enough. You will find out where the passwords are, how long it takes and who to call: exactly the things you don't want to be working out on the day itself.

How we do it ourselves

Our backups are handled by our sister organisation Xyphen IT, so they are not stored on the server itself. That is for the reason given above: a copy next to the original does not survive the loss of that original.

If you want to know how many versions are kept for your environment and how a restore works with us, just ask support. We think it is a fair question and give you a concrete answer instead of "that's taken care of".

What we don't do here

We are not a backup provider, and we don't offer a separate backup service for equipment that is not hosted with us. Our backups are part of the hosting you buy from us. If you are looking for a solution for workstations, office servers or a broader recovery strategy, that is a different kind of service from ours, and we would rather tell you that now.

Further reading

Was this article helpful?

Still stuck?

Send us a message. We will help you, usually within one working day.