Minecraft server backups: save and restore the whole setup

Identify the full recovery set

Record the server implementation, game version, Java version and installed extensions. Locate the world named by level-name and any additional worlds. Different implementations can arrange dimensions differently, so do not assume that one folder contains everything.

Include configuration, access lists and plugin or mod data. If your economy or permissions use MySQL, arrange a consistent database export as well. A game-server snapshot does not necessarily include a separate database service.

Keep a short record containing the date, game version and last configuration change. This makes it easier to select the right recovery point when several administrators maintain the same server.

Make a consistent backup

1. Notify players and finish ongoing operations.
2. Shut the server down cleanly through its console or panel. Wait for saving and process termination.
3. Copy worlds, settings and extension data while they are no longer changing.
4. Export external databases using their documented tools during the same pause in writes.
5. Download a copy outside the server’s storage and check that the archive opens and contains the expected files.

A snapshot system may provide another consistent approach. Check which data it includes and how it handles open files. Saving the current world is not the same as keeping an independent historical recovery point.

Prove that the backup can be restored

Prepare an isolated installation with matching versions and no connection to production databases. Stop it, import the saved files and configure world paths. Restore any required database into a separate test database.

Join with a player and check a known location, inventory, permissions, a container and an important plugin feature. Restart again to confirm persistence. Files existing on disk are not enough to establish successful recovery.

Before restoring production, preserve its current state too. Replace data only while the server is stopped. Tell the group which point you selected: progress made after that backup will not be present.

Choose retention around the group’s needs

Set a frequency based on how much progress players can accept losing. Keep several recovery points, including copies from before updates and mod changes. Check storage limits, expiry and download access before relying on included backups.

If a restored world develops the same issue again, investigate the underlying cause. Repeatedly rolling back a world does not fix an extension that keeps corrupting its state.

Frequently asked questions