Minecraft verwalten · 6 min read
Restore a Minecraft world from a backup
If a Minecraft world appears damaged after an update or has been accidentally replaced, first secure the current state. Then choose a backup from the time before the error and test it with the appropriate game version. Only when the correct game level is loaded, you open the server again for the group. Managing your instance you can reach through your customer panel for [Minecraft server].](/minecraft-server/).
Limiting the level of play concerned
Determine when the error occurred first. Check whether the server doesn't start at all, load a new empty world or only lack data in individual locations or certain players. For example, a new world can arise when the configuration points to another folder. In this case, a complete recovery may be unnecessary. Hold on to which version is running and which files have been last changed.
When other players report the error, please ask them for a specific location, time and description of the missing game score. Distinguishing between the actual world and the data of individual players. Some plugins store inventory or progress separately. If only this data is missing, a complete exchange of the world folder can reset unnecessarily much progress. Also check with a modpack whether the same version is active on the server and with the players.
Secure the current state before replacement
Plan a maintenance window, cancel the interruption and stop the server in order. Wait until the process is finished. Then copy the current world and the corresponding configuration to a separate location. Also, a damaged world may still contain usable parts. This copy also allows you to return to the state prior to the recovery attempt. Use a unique name with date and instance for it.
Keep both the backup and the original archive from which you want to restore. Unpack or check the archive in your own directory. This allows you to see whether it contains the world files directly or has an additional folder above them. Before copying, check the free space for the unpacked files. If there is too little space, the transfer can stop in the middle of the process and leave an incomplete state behind.
Select the appropriate backup
Select the most recent known working state before the error. For multiple backups, a protocol with creation time, game version and last major change helps. Check which dimensions and player files are included in the archive. If you want to restore a full instance, configuration files and separately stored data from extensions are also included depending on the build. An archive with the correct date is only a good candidate if its content fits the desired recovery scope.
If you have to go back after a version change, take a copy from the time before the conversion. Open it with the server version at that time and the corresponding plugins or mods. Loading an already updated world with an older version can cause problems. Keep the archives of the different versions separate, so that when another attempt is made, it remains clear which files are unchanged and which have already been loaded by a server.
Cleanly use the world folder
If your instance management offers a recovery for the present backup, check the selected backup state, destination and scope before starting. If you manually restore the current world after it is backed up, you will move it from the active path and completely discard the selected copy. Simply overwriting individual files can mix old and new data. Also, check that no additional folder level has been created when unpacking.
On a Java server, check level-name in server.properties to see which world folder the server should open. Verify that the name matches the folder you restored and keep the dimensions in their original layout. Before starting, decide which other worlds or plugin databases you also need to restore. Backups from different times can leave world and plugin data out of sync.
Check the world before release in game
Start the server with the version suitable for backup and follow the console messages. If the server breaks again when loading, secure the first meaningful error message. Check whether a folder, file or extension is called. If necessary, you can use the [Help Center].](/hilfe/) Preparing a request. Name instance name, time, versions used and the steps to the error. Remove passwords and private chat lines from the log extracts.
When the server starts, log in and check a known location, a player inventory, and the dimensions used on your server. Let a team server control a second person's known area or inventory, so you can see differences that can be hidden with a single account. Also check whether plugins, registration list, and access work as expected. A successful connection on its own does not confirm that the right world has been loaded.
Documenting the way back and release
After the tests, inform the group of the progress that you may have lost and what progress you may have lost. Note when you have restored, which archive has been used and which tests have been successful. If further problems have been identified after the release, this list will be the starting point for the next diagnosis. Delete the secured output files only when the recovery is checked in actual operation.
Then create a new backup of the confirmed stand and name it clearly. Keep the original copy and the recovered stand separate as long as you need both for a possible return journey. If the trigger was an update, plan the next attempt with a separate copy. So the group can continue playing while you check the new version.
Frequently asked questions
Why does a new world appear after the launch?
Check the world name, location of the unpacked folder and its structure. If the server does not find the expected folder, it can create a new game state.
Do I need to reset all files of the instance?
This depends on the error and scope of the backup. In case of a complete recovery, configuration and separate extension data may be required in addition to the world.
Can I open an already updated world with an older version?
For a return journey, use a backup from before the update. Test the old server version with this stand in a separate environment before replacing the running instance.
When can I release the world?
As soon as the server starts clean and a test in the game confirms the expected status. Check known places, at least one inventory and the used dimensions.