Your Host Has Backups. You Still Do Not Have a Backup.

Most hosts back up your server. Most of those backups live on the same machine, are overwritten daily, and have never been restored. Here is what to check before you need them.

GameHostReviews Editorial · · Updated

Ask a host whether they take backups and the answer is yes. Ask three follow-up questions and the answer changes shape considerably.

This is not usually dishonesty. Hosts genuinely do take backups. The gap is between what a host means by the word and what you assume it means.

The three questions

1. Where do the backups live?

If the answer is "on the same machine", they are not backups. They are copies. They protect you from deleting a world folder by accident, which is a real risk and worth having. They protect you from nothing that happens to the machine — disk failure, a node being decommissioned, an account suspension.

2. How many are kept, and for how long?

Many hosts keep one, overwritten daily. That is enough for "I broke it an hour ago" and useless for "a griefer wrecked the base on Tuesday and nobody noticed until Friday". Corruption and vandalism are both frequently discovered days late, and a single rolling backup will have overwritten the good copy by then.

3. Has anyone ever restored one?

This sounds rhetorical and is not. A backup nobody has tested is a guess. Ask support what the restore process is — self-service in the panel, or a ticket? How long does it take? Can you restore a single world without rolling back everything else?

If restoring means opening a ticket and waiting, then your recovery time is their support queue, whatever the backup schedule says.

The version that actually works

The old 3-2-1 rule is unglamorous and still right: three copies, on two different kinds of storage, one of them somewhere else entirely.

For a game server that means:

  • The live server.
  • The host's own backup, whatever it is. Free, automatic, and not yours.
  • A copy you pull down yourself, on a schedule you control.

The third one is the entire point, and it is the one almost nobody does. It is also not much work: SFTP into the server, pull the whole directory, keep the last few. A scheduled task on a machine you already own will do it.

What to actually copy

Take the whole server directory, not just the world. Specifically, you want:

  • The world or save folder, obviously.
  • Config files — server settings, and per-mod or per-plugin configuration. This is the part people regret losing, because it is invisible until you try to reproduce it.
  • The mod or plugin set, with versions. "Latest" is not a version. A modpack that worked on Tuesday may not build the same way today.
  • Permissions, whitelists and ban lists.

Do it before you need it

Restore your own backup once, onto a fresh server or locally, while nothing is wrong. It takes an evening and it tells you whether the copy you have been diligently taking actually contains a working server.

Most people find out their backup was incomplete at exactly the moment they needed it to be complete. That is a bad time to learn it.

What to look for when comparing hosts

  • Backups stored off the server's own node
  • More than one retained, with a stated retention period
  • Self-service restore from the panel, no ticket
  • SFTP access so you can take your own copy
  • A clear statement of what happens to backups on suspension or cancellation

None of these are exotic, and hosts who do them well are usually happy to say so. Vagueness on this specific topic is worth noticing.

Compare hosts for these games

Frequently asked questions

Match the interval to how much play you are willing to lose. A weekly build server is fine on daily backups. A server where a session represents hours of progress wants one before and after each session. The right question is not how often, but how much work a restore would erase.

Usually not for long, and sometimes not at all. Suspension for non-payment often deletes the server and its backups together, on a shorter timer than people expect. If billing is ever in doubt, pull a copy down first.

The world alone will get you running, but you will lose the configuration, permissions, plugin settings and mod versions that made it behave the way it did. Take the whole server directory — it is rarely much larger, and rebuilding config from memory is miserable.

Been through this yourself? Your review helps the next person.

Write a review