The Right Way to Back Up a Minecraft Server (and Restore Without Losing Anything)

Why one backup is not enough

Most server owners learn this the hard way: they have one backup file from last week, the world corrupts mid-Sunday, and the only restore point loses 6 days of progress.

A proper backup strategy follows the 3-2-1 rule: 3 copies, on 2 different storage media, with 1 off-site. Adapted to a Minecraft server, that means:

1. Hourly snapshots kept for 24 hours (fast restore from a small accident) 2. Daily archives kept for 14 days (recover from yesterday's grief) 3. Weekly off-site copies kept for 2 months (recover from full host failure)

What to actually back up

It's not just the world folder. A clean backup contains:

• world/ (plus world_nether/ and world_the_end/ if you have them)
• server.properties
• ops.json, whitelist.json, banned-players.json, banned-ips.json
• plugins/*/config*.yml (every plugin's config folder)
• plugins/CoreProtect/database.db if you use it
• The mod list (mods/ for Forge/Fabric)

Skip: logs/, crash-reports/, cache/, libraries/, the server JAR itself.

Hot vs cold backups

A hot backup runs while the server is up. Risk: chunks being written mid-copy = corrupt region files. Fix: run save-off and save-all flush before the copy, then save-on after.

A cold backup stops the server, copies, restarts. Always clean, but causes 30–60 seconds of downtime.

For a small server, hot backups with the save-off trick are fine. For a public server with 50+ players, schedule a 2-minute weekly cold backup window.

On FreeMCHost

Backups are built in. From the panel:

1. Backups tab → "Create backup" → a snapshot is taken with save-off applied automatically. 2. Backups are stored on a separate node, so a node-level failure doesn't take them down. 3. Free tier keeps the 2 most recent backups; paid plans extend retention.

For the 3-2-1 strategy, download one backup per week via the panel and store it on your own machine or a Google Drive folder — that's the "off-site" copy.

Restoring without losing player inventories

A common mistake: restore the world from yesterday, and every player who logged in today loses their inventory. Why? Player data lives in world/playerdata/<uuid>.dat — restoring the world overwrites it.

Clean restore procedure:

1. Stop the server. 2. Move (not copy) the current world/playerdata/ folder somewhere safe. 3. Restore the backup. 4. Move the saved playerdata/ back into the restored world. 5. Start the server.

Players keep their inventories, but the world rolls back. Best of both.

Testing your backups

A backup you've never restored is not a backup — it's wishful thinking. Once a month, spin up a second server on your hosting plan, restore the latest backup to it, and check that:

• The world loads without errors in the console
• Player data is intact (log in with your account)
• Plugins start cleanly

10 minutes a month, peace of mind forever.

Related

• [Anti-grief guide](/blog/minecraft-anti-grief-guide)
• [Optimize Minecraft server performance](/blog/optimize-minecraft-server-performance)
• [OP players & permissions](/blog/how-to-op-a-player-and-manage-permissions)