Minecraft verwalten · 6 min read
How to back up and verify a Minecraft world
A Minecraft backup should bring you back to a known game level after an incorrect update, a deleted folder or a failed conversion. To do this, you need a consistent copy of the world and the information that can be used to re-open it.](/minecraft-server/) you start in the administration of the concerned instance.
Choose the right time for backup
Make a backup of changes that can change a world permanently. These include version changes, new mods, a world folder exchange, and larger configuration work. Also, keep a regular schedule in the current project. If you want to lose at most one evening game progress, there should be little time between two backups. The need depends on how often your group actually plays.
Mark the last working state before a major change. Write down date, instance name and game version. In a modpack, the exact pack version is also included. You will see later which copy belongs to which server stand. For a return journey, a cleanly named older state is often more valuable than the latest copy, if it only occurred after the error occurred.
View the world and configuration together
Identify the world folder the server actually loads. In Minecraft Java, check level-name in server.properties. Depending on the server software, dimensions may have separate folders. Follow the layout of your existing instance and include all related folders. Otherwise, the restored copy can be missing the Nether, the End or individual player data.
Also check what is outside the world. For a complete move or a return journey after an update, settings, admission list and data from plugins or mods can be important. Some extensions use a separate database. Then the team must also schedule a suitable backup for this. Determine which data is contained in your archive and where you can find a copy of the other files.
Create a consistent copy
For a manual file copy, a scheduled, ordered stop is a simple way. Quit the interruption, let the group leave the game and wait until the server process is finished. Only then do you copy the files. If the process continues to write during an ordinary file copy, individual files can come from different times. This can be difficult to diagnose when recovering.
If you use the instance management backup function, check its scope and status of the backup job. If possible, open the files only when the backup is complete. After maintenance, test an accession and then release the server. If you are unsure of an error message or the scope of the backup, you will find the contact option in the [Help Center].](/hilfe/).
Check archive and free memory
Watch for free storage before you place large worlds as an archive. The original, an unpacked copy and an archive can temporarily occupy space at the same time. Depending on the world, the amount of data increases when players explore new areas or store plugins further data. Plan for backup operations Reserves and keep older working copies until the new status is checked.
See if the archive is readable and contains the expected folders. File size alone is not enough as a check. An archive can be opened and still contain the wrong world folder. Compare the structure contained with the active instance. When you download a copy, check if the transfer has been completed. A checksum is helpful to compare two saved copies of the same file.
Keep copies separately
Keep at least one important copy separate from the running instance. If world and all backups are in the same place, accidental deletion or memory problems may occur. Limit access to people who need backup for operation. World files and plugin configurations may contain personal data or access information. Therefore, do not send complete archives via public chat channels.
For example, you can stack current copies more densely and keep older stands less frequently. Keep a stand before a big version change until the new server has proven its worth. If you have to release space, first check that at least one other complete and readable copy is retained. Write down in the team who creates backups and who can access the separate copy in case of a fault.
Play the restoration once
The most meaningful test is a recovery in a separate environment. Use the appropriate Minecraft version and the same extensions as when you are back up. Check known locations, at least one player inventory and the dimensions your group uses after launch. This allows you to see if the files have been fully transferred, but the wrong world name is configured for example.
If you don't have a separate instance available, you can still unpack the archive and check folders and versions. Note that the start test is still pending. Also, write down how to get back to backup from the current state in case of an emergency. To do so, set the path to backup, the required versions and the responsibility in a place that the team can reach even if the game instance fails.
A test protocol does not have to be extensive. Write down when the backup was created, which instance you used for the test and which tests were successful. Note deviations, such as an extension that could only be loaded after an additional setting. If several people maintain the server, a second person can use these notes to check whether they could restore the status independently.
Frequently asked questions
Is it enough to copy only the world folder?
This can be sufficient for the pure world status if all corresponding dimensions and player data are included. For a complete restart you check the configuration, plugins, mods and possibly external databases.
Do I have to stop the server for every backup?
An orderly stop is useful for simple manual file copying. If a built-in procedure supports running backups, check its documentation and check which files it records.
How do I recognize a useful backup?
The archive must be read and contain the expected files. The most reliable proof is a successful start of a separate copy with the same versions and a test in the game.
What copy do I keep before an update?
Keep the last working status before the update, including the configuration and the required version information. This gives you a clear way back if a world or extension is causing problems after the conversion.