A useful game backup must capture a consistent world and the settings needed to run it. Copying a folder while the server is actively writing can leave you with an incomplete recovery point. Plan a short maintenance window before a software upgrade, plugin installation or major map change.
Recommended steps
- Notify players and record the current server software, game version, startup settings and installed modifications. Note which directories contain worlds, player data, permissions and configuration files.
- Use the game's supported save procedure and stop the service cleanly where needed for a consistent copy. Confirm that the server has finished saving before archiving its data.
- Copy the relevant data to storage separate from the running server. Label the backup with the date, game version and reason for the change. Do not overwrite the only known working copy with an untested new archive.
- Check that the archive can be opened and that important files are present. Where practical, restore into a separate test instance using a compatible version and verify world loading, player data and permissions.
- Make the planned change, start the server and review its log before reopening player access. Test essential functions and retain the pre-change copy until the new setup is stable.
An upgrade may change a world's data format, and simply downgrading the server software can be unsafe. If rollback is necessary, restore the matching world and configuration together. Remember that restoring a backup can remove player progress made after that recovery point.
