Restoring a world from a backup without making things worse
A player blew up half the spawn, a plugin corrupted inventories, or a mod update wiped some chunks. The backup exists, it's recent — and yet the restore goes wrong half the time. Almost always for the same reason: it was started while the server was still running.
Order matters: stop, isolate, verify, restore
- Stop the server cleanly. Not a kill — a real
stop. Minecraft keeps part of the world in memory and only writes to disk at intervals. A hard stop during a write is exactly what produces unreadable region files. - Isolate the current state before touching it. Copy the damaged world, damaged as it is. A restore that overwrites the current state removes any way back if the backup you picked turns out to be older than you thought.
- Verify the backup before using it. Its date, its size, and its contents if you can. A 2 MB backup where the previous ones were 400 MB isn't a backup, it's an incident nobody caught.
- Restore, then restart. And only then let players back in.
Picking the right restore point
The instinct is to grab the most recent backup. That's often wrong: if the incident happened hours ago and nobody noticed, the latest backup already contains the damage. Rebuild a rough timeline first — server logs and chat history help a lot — then pick the point before the incident, even if it costs a few hours of play.
Restoring the world isn't restoring the server
A server is the world, but also plugin configuration, permissions, and sometimes a database (economy, land claims, statistics). Restoring only the world folder while leaving the rest as-is produces inconsistencies: claims protecting empty areas, an economy that no longer matches what's in the chests.
Decide explicitly what you're restoring, and tell players what will be lost. A community copes fine with losing two hours of progress; it copes far less well with finding out afterwards.
Afterwards: make the next incident cheaper
- Test a restore before you need one. A backup never restored is a hypothesis, not a guarantee.
- Check how often your automatic backups actually run and how many are kept — the details for our plans are on the pricing page.
- Reduce the need to restore at all: a targeted rollback plugin lets you undo one player's damage without touching the rest of the world. See our anti-grief plugin picks.
The step-by-step procedure in the panel is covered in the backups documentation.