Prerequisites
- The game's official server documentation
- A maintenance window
- Independent backup storage
Security note
Copying live world files may produce an inconsistent backup. Use the game's save, flush, pause, or clean shutdown procedure before capture.
Step 1
Find every stateful path
Record world or save directories, configuration, allowlists, bans, admin data, mods, plugin data, and service definitions.
Step 2
Create a consistent save point
Notify players, invoke the game's supported save operation, and pause or stop the server when its documentation requires that for consistency.
Step 3
Copy data outside the server
Store versioned backups in independent storage with restricted access. Include a manifest with game version, mod versions, and capture time.
Step 4
Apply retention and monitoring
Keep several recent versions plus less frequent historical copies. Alert when backup age, size, or job status is unexpected.
Step 5
Test an isolated restore
Restore to a separate directory or test instance, confirm world load and player state, then document exact recovery steps.
Step 6
Back up before upgrades
Take a verified recovery point before game, mod, plugin, operating system, or control panel changes.
Troubleshooting
- The restored world is older than expected
- Check the backup timestamp, time zone, save command result, and whether the live server wrote to a different instance or path.
- Mods fail after restore
- Restore the matching game, mod, and configuration versions or follow the mod authors' documented migration path.
Frequently asked questions
How often should a game server be backed up?
Set frequency from the amount of player progress you can afford to lose, then confirm the backup process does not disrupt the server.