Minecraft Server Backups: What to Back Up and How Often
A practical backup plan for Minecraft servers — which files matter, taking consistent backups while the server runs, how often, how long to keep them and testing restores.
On this page
Every long-running Minecraft server eventually needs a backup: a griefed spawn, a corrupted chunk, a plugin update that wiped data, an accidental /kill @e, or a world that won’t load after an upgrade. When that day comes, the only question is whether a good backup exists. This article covers what to back up, how to do it safely and how often.
What to back up
Worlds
On Paper and Spigot, each dimension is a separate folder:
world/— the Overworld (plus player data and stats)world_nether/— the Netherworld_the_end/— the End
Vanilla and most modded servers keep all dimensions inside a single world folder instead. Back up every world folder, including any extra worlds you created with a multiworld plugin.
Plugin and mod data
plugins/— plugin JARs, configs and data (homes, claims, economy balances, warps). For plugins that store data in a database, the folder has configs but the data lives in the database — see below.mods/andconfig/on modded servers — the exact mod set and configs that go with the world.
Server configuration
server.properties,bukkit.yml,spigot.yml, and Paper’sconfig/fileswhitelist.json,ops.json,banned-players.json,banned-ips.json- your start script or JVM flags
These are small and painful to recreate from memory.
Databases
If LuckPerms, CoreProtect, an economy plugin or a web map stores data in MySQL or PostgreSQL, the world backup doesn’t include it. Dump databases on the same schedule:
mysqldump --single-transaction -h HOST -u USER -p minecraft > minecraft-$(date +%F).sql
See connecting Minecraft plugins to MySQL.
What you can skip
Server JARs (re-downloadable), logs/, cache/, libraries/, and crash reports (unless you’re investigating something). Leaving these out keeps backups smaller.
Take consistent backups
Copying world files while the server is writing to them can capture a half-saved chunk. There are two safe approaches:
Pause saving during the backup
From the console:
save-off
save-all flush
# ... copy or archive the world folders ...
save-on
save-off stops the server writing chunks to disk, save-all flush writes everything pending, and save-on resumes normal saving afterwards. Your players keep playing throughout.
Stop the server
For the most certain consistency — before major updates, for example — stop the server, back up and restart.
Many backup plugins and hosting panels automate the pause-and-copy sequence for you.
How often
| Server | Suggested schedule |
|---|---|
| Small friends server | Daily |
| Active community server | Daily, plus before every update or big event |
| Busy public server | Every few hours, plus daily and before updates |
Always take a manual backup before updating Minecraft versions, updating or adding plugins, changing world generation settings, or running large WorldEdit operations. See updating your server to a new Minecraft version safely.
How long to keep them
Keep a rotation, not just the latest copy. Problems are often discovered days later — a griefed build nobody noticed, a corrupted region that only shows when someone visits.
A sensible rotation:
- Daily backups for the last 7–14 days
- Weekly backups for the last month
- A copy before each major version upgrade, kept until you’re confident the upgrade is stable
Keep a copy somewhere else
Backups stored only on the same server protect you from mistakes, but not from losing the server itself. Follow the 3-2-1 idea: three copies of your data, on two different kinds of storage, with one off-site. For most servers, that means the host’s backups plus a periodic download of the latest archive to your own computer or cloud storage.
Test a restore
A backup you’ve never restored is a hope, not a backup. Once, and after any change to your backup process:
- Restore a backup to a test server (or a copy of the server).
- Start it and join.
- Check that the world loads, builds are intact and plugin data (homes, claims, ranks) is present.
It takes twenty minutes and turns a stressful emergency into a routine task.
Restoring for real
For a full rollback: stop the server, move the current world folders aside (don’t delete them yet), copy the backup in, restore the matching database dump if you use one, and start the server.
For targeted damage, a full rollback often isn’t necessary:
- Griefing: CoreProtect rollbacks undo specific players’ changes without affecting anyone else. See essential plugins for a new survival server.
- A single damaged area: tools like WorldEdit schematics or region-level restores can replace one area from a backup.
Backups and disk space
Large worlds make large backups. A pre-generated 5,000-block radius world multiplied by two weeks of daily backups takes serious space. Compress archives, exclude unneeded folders, and prune old backups on schedule. When planning server storage, include backup retention — see pre-generating your world with Chunky.
Backups on Kerit Cloud
Every paid Kerit Cloud Minecraft server includes daily automated backups, and the free MySQL or PostgreSQL database that comes with every paid server is backed up daily too. You can still take manual backups before updates and download copies for your own off-site storage through the panel’s file manager or SFTP.
Summary
Back up every world folder, plugin and mod data, server configuration and any databases your plugins use. Take consistent backups with save-off, save-all flush and save-on (or with the server stopped), at least daily and before every update. Keep a rotation of daily and weekly copies, store one copy off-site, and test a restore before you ever need one.