Minecraft · Backups
A backup you have never restored is a hope, not a plan.
Most people only think about backups on the day they need one. The work that actually saves a world happens earlier: knowing what is being copied, taking clean snapshots, and proving a restore works before it matters.
A backup is files, not a save state
A running Minecraft server keeps two versions of reality. Some of it lives on disk, written out as players move and chunks unload. Some of it lives only in memory: the exact position of a mob mid-jump, the contents of a chest that was opened a second ago, the state of a redstone circuit that is active right now.
A backup copies the first and cannot copy the second. That is not a flaw; it is what a file-level backup is. The practical consequence is that the cleanest backup is taken when the server is not actively writing, because a copy taken mid-write can capture a file halfway through a change.
What actually gets backed up
It helps to know exactly what a full server backup contains, so you can spot the gap when it does not contain something you relied on.
| Item | In a full backup | Detail |
|---|---|---|
| World folders | Yes | Region files, level.dat, player data, stats and advancements for the overworld, nether and end. |
| Datapacks | Yes | Stored alongside the world, so custom recipes, loot tables and functions travel with it. |
| Plugin and mod configs | Yes | The plugins and config folders, which hold the settings your world depends on. |
| Server settings | Yes | server.properties plus the whitelist, ops and ban lists that define who can do what. |
| Live in-memory state | No | Whatever has not yet been written to disk exists only in the running process and cannot be copied. |
| External data | Depends | Anything a plugin stores outside the server directory, such as a separate database, needs its own plan. |
Scheduling: the trade-off nobody mentions
The instinct is to back up as often as possible. The reality is that every backup costs disk space and a little server work, so the question is not how often you can back up but how much you are willing to lose.
- Pick a frequency that makes the worst realistic loss acceptable. If players build every evening, a backup that runs daily leaves a day of building exposed.
- Ask the server to finish writing before a file-level copy. Saving the world first, or stopping the server for the copy, gives a clean archive rather than a torn one.
- Keep more than one generation. A rotation that keeps several recent backups means one bad snapshot cannot erase your last good state.
- Store a copy somewhere other than the server itself. A backup that lives only on the same disk disappears with the disk.
Before anything risky
Taking a manual backup before a software change, a major plugin or mod update, or a large world edit is the single highest-value habit in this guide. It costs a minute and it turns a mistake into an inconvenience.
The restore drill
Here is the part almost everyone skips. A backup is only proven when you have restored it and watched the world come back. An archive that has never been opened might be empty, corrupt, or missing the one folder that mattered, and you will not find out until the day you need it.
- Take a fresh backup, then set up a second server to test with, so the drill cannot touch your live world.
- Stop the test server, replace its world with the contents of the backup, and start it again.
- Check the things that matter: does the world load at spawn, are player inventories present, and are plugin or mod settings intact?
- Note how long the restore took. That number is what you are really risking when you skip a backup.
- Repeat on a schedule, and mark which archives you have actually tested so you are not trusting an untested one by accident.
The point is not ceremony. It is that “we have backups” and “we have restored from them” are two different claims, and only the second one holds up under pressure.
Where Rynox fits in
Every Rynox server gives you file access through the panel, which is where manual backups and restores happen: download the world, keep a copy, and put it back when you need it. Automatic backups are part of the plans, and how many are kept depends on the tier you are on, so check the plan you are considering rather than assuming a single figure.
The storage question is real here too. Backups multiply the space a world takes, and a server that has been running for months is larger than the one you started with. The cost and sizing page explains how storage and retention scale with a plan, and the pricing page lists what each tier includes.
Backups — questions
How often should a Minecraft server back up?
Often enough that the worst realistic loss is acceptable, and no more often than your storage can carry. For a quiet server that might be daily; for a busy public one where players build constantly, more frequent snapshots shorten the window you would lose. Frequency is a trade-off between space and the size of the gap you are willing to accept.
Are automatic backups enough on their own?
They are a strong baseline but not a complete strategy. A single automated copy can be overwritten, can fail silently, or can capture a world that was already damaged. Keep a manual backup before anything risky, and keep more than one copy so a bad state cannot overwrite the last good one.
Why is a backup taken while the server is running sometimes imperfect?
Because the world is still being written to disk as the copy is taken. A file can be captured halfway through a change, so the archive holds a mixture of old and new data. Asking the server to finish its writes first, or stopping it briefly, gives a clean, consistent copy.
Does a backup include my players and their builds?
Yes. Player data, inventories, statistics and every block that was saved to disk are inside the world folders, so a properly restored backup brings the builds and the players back together. Only changes still in memory at the moment of the copy are at risk.
Back up before you need to, and test the restore.
Panel file access and automatic backups are part of every Rynox plan, with retention that scales with the tier. Compare what each plan includes on the pricing page.