A complete Minecraft server backup saves worlds, player data, configuration, extensions and, where applicable, external databases as one consistent state. For a manual file copy, you first stop all writing processes. Whether the backup is usable only becomes clear with a restore using the documented versions and a check of structures, inventories and plugin data.
Step by step in the customer panel (with video): Create and restore a server backup
What Belongs to the Save State
| Component | What may be missing if omitted |
|---|---|
| All world folders and dimensions | Structures, explored areas, Nether, End or mod worlds |
| Player data | Inventories, positions, progress and statistics |
| Configuration and access rules | World name, game rules, whitelist and operators |
| Mods, plugins, datapacks and their data | Machines, claims, economy or additional game rules |
| External databases | Permissions, balances or other data stored outside the server folder |
| Version note | The server and runtime combination needed for restoring |
Back up the complete server contents instead of picking individual folders from a generic path list. World layouts change with server software and version. In particular, the formerly common split into world, world_nether and world_the_end is not a universal rule for current versions. Check the actual folders and the active world name. The Paper migration reference distinguishes between old and new formats.
Checking Backups in the Panel
Open Backups for the selected server. Check the time and completion status of the existing backups. When you create a new backup, wait for the finished result. A started job or a progress bar is not yet an available restore.
Check the retention and download options shown for your server. Don't infer a particular schedule from the mere existence of the tab. An additional copy outside the running server protects you even if its own storage is no longer accessible.
Manual File Backup: Stop Completely First
For a manual copy via SFTP, you stop the server and confirm that the process has ended. A quiet gaming period isn't enough: background processes can still write world and plugin files. Even a single save command doesn't automatically make a subsequent long file copy consistent.
Announce the interruption, prevent new game sessions and, after the stop, back up the files that belong together. For external databases, additionally stop their writing applications or use the database's documented consistent backup procedure. A running test instance can also write.
The SFTP guide describes file access. You stop the server via the panel; don't upload private credentials to public diagnostic reports.
Making the Backup Identifiable
Use a name with the date, server and reason, such as 2026-09-12-survival-before-update. Place a text note next to it with the Minecraft version, server software, loader, relevant extensions and backup time. Document whether external databases are included or backed up separately.
Check that the archive can be opened and the expected files are present. If you transfer the same archive, you can compare its SHA-256 checksum before and after the transfer. Matching checksums prove an unchanged transfer; they don't yet prove that the original backup was complete.
Testing the Restore on a Copy
- Prepare a separate target with the documented versions and restrict access.
- Back up any existing target state and stop its process.
- Restore the chosen backup state completely. Don't mix old world data with newer plugin databases.
- Check the active world, configuration and database connections before starting.
- Start and read the console. Compare known structures, dimensions, inventories and key plugin functions.
- Make a small test change, stop cleanly and start again. The change must still be there.
A test copy must not use a production database. Otherwise, even tests can alter the real save state. Note down the test result and keep the unchanged backup state.
Rolling Back in an Emergency
First determine the last good point in time and the progress lost as a result. Also back up the faulty current state for comparison. Then stop the target and restore the chosen complete state. In the case of a failed version change, the matching old software is part of it; downgrading the already modified world is not a restore.
Tell the players from which point in time changes are missing. Check the world with a normal account and only then publish the connection details again or open access. If only the wrong world was active, first clarify the world name instead of hastily resetting all data.
Planning Frequency and Storage
Decide based on the maximum progress you're willing to lose. If a group builds large projects every day, a weekly backup may be too coarse. Additionally create a clearly labeled backup before changes. Keep several points in time, because an error may only be noticed later.
Measure actual archive sizes and free storage. Plan space for backups, their unpacked restore and further world growth. Blanket compression ratios or fixed world sizes are unreliable for this.
FAQ
Is a copied world folder enough?
For a full server restore, usually not. Extensions, permissions and external data can also be part of the save state.
Can I open the only backup to test it?
Work with a copy. Even loading it in a new version can change data.
The restore starts, but players have no items. What now?
Stop further changes and first compare the active world name, backup time and the existing player data. Then check whether the server recognizes the player via the same authentication and proxy path as before the restore: a differing UUID entry can look like a new inventory. Don't blindly change online-mode for this and don't rename data files on a hunch. Back up the faulty state and restore the matching configuration together with the associated player data on a copy.
Related Guides
- Missing Minecraft Chunks: Assess the Damage and Rescue
- Minecraft Loads a New World: Finding the Old Map Again
This Guide in Other Languages
English · Español · Français · Nederlands · Português · Русский