Minecraft Server Backup Best Practices
Every Minecraft admin has the same wake-up call: a world they built for a year, gone in one bad update. Here's the backup routine that makes sure it never happens to you — and the one step almost everyone skips that costs them the world anyway.
TL;DR
- Back up the world daily, configs on change, and always before a risky update
- Follow 3-2-1: three copies, two storage types, one off-site
- Snapshot safely (never copy a live world folder mid-write)
- Test the restore monthly — an untested backup is a hope
What to back up (and what to skip)
Back up: the world/ folder (and world_nether/, world_the_end/ if split), plugins/ and their configs, server.properties, whitelist.json, ops.json, banned-players.json. For modded servers, config/ and mods/ too.
Skip: the server jar (re-downloadable), logs/, cache/, libraries/ (re-downloadable). Backing these up just makes every backup slower and larger for no recoverability benefit.
How to snapshot a running server safely
The classic mistake: cp -r world backup/ while the server is live. Minecraft writes region files continuously — if you copy mid-write, you capture a corrupted chunk. On restore, that chunk errors out or resets.
The safe methods, in order of preference: (1) a panel's built-in backup button (it pauses writes and snapshots correctly — this is what CoalHost does), (2) a plugin like DriveBackupV2 or a filesystem snapshot (ZFS/Btrfs), or (3) manually run /save-off + /save-all, copy the world, then /save-on. Manual works but freezes world saves while you copy — fine for a quick copy, bad for a busy server.
The step everyone skips: test the restore
A backup you've never restored is a file that might be empty, corrupt, or missing the one folder that mattered. The horror stories are always the same shape: “we had backups!” — then the backup was a 0-byte file, or the restore script had a path bug nobody noticed for six months.
Once a month, take the latest backup, restore it to a scratch server, and boot it. Check the world loads, a few known builds are intact, and player inventories are there. Ten minutes a month. It's the difference between losing one day of progress and losing everything.
The off-site copy is non-negotiable
If your backup lives on the same machine as your server, a host failure takes both. The 3-2-1 rule exists because of this: keep the live world, a local backup, and an off-site copy. The off-site copy can be cloud storage, another host, or a second datacenter — anything that survives your primary machine dying.
On a panel host, check whether backups are stored separately from the server VM (CoalHost keeps snapshots on independent storage, so a VM loss doesn't take the snapshots with it). If you self-host, automate an encrypted off-site sync — rclone or restic are the standard tools.
FAQ
How often should I back up my Minecraft server?+
Daily for the world, and on-change for configs and plugins. A daily world backup means the worst case is losing one day of progress. More active or public servers should back up every 6–12 hours. Always take a manual backup right before a risky change (modpack update, world edit, plugin swap).
What actually needs to be backed up?+
The world folder (region files, player data, advancements), the plugins/ and config folders, and server.properties + whitelist/ops/banned lists. You do NOT need to back up the server jar — you can always re-download Paper/Forge. Backing up logs and cache folders just wastes space.
What's the 3-2-1 rule for Minecraft?+
Three copies of your world: the live one, a local backup, and one off-site. Two different storage types (e.g. server disk + your own machine), one copy off-site (another host, cloud storage, a second datacenter). If your host's whole machine dies, an on-server backup dies with it — that's what the off-site copy is for.
How do I know my backup actually works?+
Test the restore. A backup you've never restored is a hope, not a backup. Once a month, restore the latest backup to a scratch server and boot it — check the world loads, inventories are intact, and the seed/structures match. This is the step everyone skips and the one that matters when disaster hits.
What's the safest way to back up a running server?+
Don't copy the world folder while the server is writing to it — you can capture a half-written region file. Either use a plugin/panel that snapshots with the server paused or use a filesystem snapshot, or run `/save-off` + `/save-all` + copy + `/save-on`. On panel hosts, use the built-in backup button, which does this safely for you.
Backups you never have to think about
CoalHost snapshots your world automatically before risky changes and stores them off the VM — with one-click restore.
View Minecraft Hosting →