How to restore a Minecraft world to a new server

Technical Support
1

OS Name/Version:
Debian 12 (bookworm)

Product Name/Version: AMP Release “Phobos” v2.6.2 built 17/06/2025 09:10

Problem Description:
My last server crashed irrevocably after a HDD died, and I’m working to rebuild my instances. I had backups running for all of my game servers every 3 hours, and I have those .zip backups stored on another drive.

I have a new version of AMP deployed on my VM and am attempting to restore my backups to new instances that I’m creating on AMP, starting with Minecraft Bedrock edition.

I’ve tried following the steps on How to import an existing Minecraft server into AMP

  1. Created a .zip of my backups /Minecraft/ folder
  2. uploaded it via SFTP
  3. extracted the .zip the AMP process (confirmed that amp:amp own’s the file after uploading)
  4. Right click on the server.properties file and choose import, says “0 settings imported”
  5. Start the server, and the server boots up, but does not restore my settings, just a brand-new world, none of my previous progress.

When I check the AMP configuration/Minecraft Bedrock settings, it shows the default world info.

If I check the file server.properties.save, it shows all of the previous configuration settings (custom name, and world seed number). I’ve tried renaming this file to server.properties and importing the file. Or just replacing the whole /Minecraft/ folder with my saved folder and it always reverts back to the default blank save world.

I’ve also attempted to restore my backups through the built-in “Backups” tab by following these steps:

  1. Copy my instance Backups from source to /home/amp/.ampdata/instances//Backups/
  2. This destination includes the .json which lists ALL my backups, and all of the related .zip files
  3. sudo chown -R amp:amp *
  4. sudo chmod 755 *
  5. Manage my Bedrock instance > Open Backups
  6. All Backups are listed
  7. Select the most recent backup and click “Restore”
  8. Wait for Restore to complete
  9. Start the instance, wait for update to complete
  10. Server boots, upon login, its a blank world with none of my previous progress.

Any advice or links to alternative documentation would be greatly appreciated!

2

I am also having this exact same issue after following the steps

3

I FIGURED IT OUT!

Soooo this was cobbled together from a few other articles. Hopefully this provides value to whomever stumbles across this write-up.

Assumptions:

  • You have a valid Backup from your AMP instance
  • You know the EXACT name of your previous instance (and any previous settings that were configured)

Steps:

  1. Create a new Instance in AMP using the EXACT name of your previous instance.
  2. Modify the configuration in AMP to reflect the settings in your previous setup. The settings I modified in Minecraft were found in my previous “server.properties” file, and I changed the “Server Name”, “Level Name”, and “Level Seed” to reflect my previous settings.
  3. Copy over your previous Backups (and the .json) into the folder /home/amp/.ampdata/instances/%nameofinstance%/Backups
  4. run the commands (in the Backups folder listed above) to change ownership and access to the files
sudo chown -R amp:amp /home/amp/.ampdata/instances/%nameofinstance%/Backups/*

sudo chmod -R 755 /home/amp/.ampdata/instances/%nameofinstance%/Backups/*
  1. Manage the instance from the webUI and look at the backups (they should be appearing now.
  2. Restore your most recent backup
  3. Stop Server, Start Server
  4. Try connecting

For me these changes worked. The secret sauce seemed to be in what I listed at the top. The WebUI Configuration needed to match EXACTLY what I had in previously before the restore would work.

It would be super helpful, if I could take a previous backup and IMPORT that from the ADS01 new instance creation screen.

OR if when restoring a backup it would also update the games Config in the WebUI to reflect the settings that were captured during the backup.

I’m going to try following these steps again with Satisfactory and Valheim.

Hope this helps someone else (probably me again in the future after I’ve forgotten how to fix this issue and need to again).

Good luck out there!

4

I just tried these steps and unfortunately it didnt work for me