How to Back Up and Restore a Minecraft Server Safely

Direct answer

The safest beginner backup is an offline backup: use the stop command, wait for the Java process to exit, then copy the world data plus configuration and plugin files to a different location. Keep multiple dated backups instead of overwriting one file forever.

What to back up

World folders / world data.
server.properties and other server configuration.
The plugins folder, including plugin configuration and data, for a plugin server.
Any proxy, permissions, database, or custom files required to rebuild the server.

Paper's update guide specifically calls out world folders, server configuration, plugin configuration, and plugin JARs as important backup targets.

Offline backup procedure

Warn players.
Run stop in the console.
Wait until the server process exits.
Copy the required folders/files to a dated archive.
Store at least one copy outside the server's main disk or account.
Start the server again.

Before updates or risky changes

Create a fresh backup before changing Minecraft versions, server software, major plugins/mods, world-generation mods, or storage layouts. Do not assume an update can always be rolled back: opening a world in a newer Minecraft version can upgrade its data, and downgrading that world is not supported.

How to restore

Stop the server first. Rename or archive the current broken folder instead of deleting it immediately, then place the backup in the expected location and verify level-name if necessary. Start the same Minecraft/software version that created the backup when possible and watch the startup log.

A backup is only real after a test restore

Periodically restore a backup into a separate test directory or test server. This catches empty archives, missing plugin databases, wrong paths, and backup jobs that silently stopped working.

Prove that the backup is restorable

Back up world, Nether/End data, plugin configurations and external databases where applicable. A ZIP of the world folder alone may not preserve all player progress.
Create a restore test in a fresh directory using the same server version; confirm world spawn, inventories, permissions and critical plugins.
Record backup time, version, size and location. Keep at least one copy off the game host so a disk failure or compromised machine cannot destroy every recovery point.

Official references

These references were checked while preparing this guide. Version-specific behavior can change, so use the project documentation for your exact release when a detail differs.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.