Back up and upgrade without losing server data
Use this checklist to prepare a maintenance window. Migration and rollback for the next release are still being qualified.
1. Stop writes and record the current installation
Set aside a maintenance window, disconnect players and stop the game services cleanly. Check the logs for successful final saves. Record the installed server and PostgreSQL versions, database location, service configuration and data directories.
2. Back up and verify the restore
Save a complete PostgreSQL backup and any required database roles. Also save the server configuration, certificates and keys, external data directories, and the exact previous binaries. Restrict access to the backup. Keep a verified copy outside the installation directory.
Restore it into a separate PostgreSQL instance and server directory. Check character state, inventory, currency, world data and the administrator login before proceeding.
3. Run the upgrade on the restored copy
Follow the migration instructions for the candidate package. Verify Game, Login and WebAdmin, then reconnect, write a representative change and confirm it survives a restart. Open the production server to players only after these checks pass for the intended upgrade path.
4. Restore the previous version if the upgrade fails
Stop the upgraded services and preserve the failed state for investigation. Restore the previous database into a fresh instance, then start the old binaries with their old configuration and matching external files. Verify the restored state before redirecting players.
Any writes accepted after the original backup may be absent after rollback. Keep maintenance enabled until you decide how to recover these writes.