Minecraft server backups and version changes

Backups in the panel

Backups live in the Backups tab. A backup contains the server files — world, configs, plugins/mods. It does not include databases from the Databases tab; if a plugin uses one, back it up separately.

The number of backup slots is set per service and shown directly in the Backups tab. When all slots are used, delete an older backup before creating a new one.

Creating a backup

For a consistent world in the backup, let the server write all data to disk first. Stopping the server is the safest option; if it has to keep running, enter in the console:

save-all flush    # write the world to disk
save-off          # temporarily disable autosave
# ...create the backup in the panel and wait for it to finish...
save-on           # re-enable autosave

1. In the Backups tab click Create Backup.
2. Fill in Backup Name, e.g. "Before updating to 1.21".
3. Optionally list in Ignored Files & Directories the files you do not want backed up (one per line). This saves space and time:

logs
crash-reports
cache
*.log
plugins/dynmap/web/tiles
bluemap

4. The Locked toggle prevents the backup from being deleted until you unlock it — useful for important milestones.
5. Click Start Backup and wait until the backup shows its size and a completed state.

Restoring a backup

1. Stop the server.
2. In the Backups tab open the backup's menu (three dots) and choose Restore.
3. In the confirmation dialog you can tick Delete all files before restoring backup. We recommend it when rolling back after a version or modpack change — otherwise new files that were not in the backup stay on the server.
4. Wait for the restore to finish and start the server.

Restoring only part (e.g. one world)

Download the backup, extract it on your computer and upload the folder you need (e.g. world) via SFTP while the server is stopped.

Regular backups via Schedules

You can set up regular backups yourself in the Schedules tab: create a schedule (e.g. every day at 4:00 — cron 0 4 * * *) and add a Create Backup task. Keep an eye on the slot count — once full, no further backup is created until you delete older ones. Schedules in general are covered in Pterodactyl panel basics.

Changing the Minecraft version

Updating to a newer version is usually smooth if your plugins and mods are ready for it. Going back to an older version after the world has been opened in a newer one, however, is not supported — the world is converted to the new format and the only safe way back is a backup.

1Preparation

• Check that your key plugins or mods have releases for the target game version. Do not update without your land protection or economy plugin being ready.
• With Paper, wait for a stable build of the new version — the first builds after a release are often experimental.
• Tell your players: the client must use the same or a compatible version.

2Backup

Stop the server and create a backup as described above, ideally locked and also downloaded to your computer. Do not change the version without a backup.

3Change the version in the panel

1. In the Startup tab find the Minecraft version variable in the Variables section (for Paper typically Minecraft Version, possibly Build Number). Enter the target version, e.g. 1.21.1. The exact names depend on the template.
2. Check the Docker Image (Java version):

   Minecraft version	Java
   1.20.5 and newer	21
   1.18 – 1.20.4	17
   1.17.x	16 (or 17)
   1.16.5 and older	8 (or 11)

3. In the Settings tab click Reinstall Server and confirm. The installation script downloads the server core in the new version. The world and configs usually stay, but a reinstall may overwrite files — which is why the backup from step 2 is essential.

4Update plugins and mods

Before the first start, replace plugins (plugins folder) or mods (mods folder) with builds for the new game version. Delete the old files to avoid duplicates. See How to install plugins.

5Start and verify

1. Start the server. The first start after an update takes longer because the server converts world data.
2. Verify the version in the console with version and check for plugin loading errors.
3. Join and check spawn, land claims, inventories and key features.
4. If something is wrong, stop the server, restore the backup with Delete all files before restoring backup ticked and set the previous version back.

[Server thread/INFO]: This server is running Paper version 1.21.1-...