Prepare your hosting environment

1. Record the baseline

Use Environment setup and the installation sequence. Keep a private operations note with the following information.

1. OS, SQL instance, server/client versions, installation folders, and last successful login test.
2. Every service’s executable, working folder, code, ports, configuration, and log location.
3. A separate test database and services: a test pointing at production SQL is not isolated.
4. Who can access the host and where backups are stored. Keep passwords in a password manager.

2. Make a recovery point

1. During maintenance, stop player activity and game services that write data. Leave SQL running for backup.
2. In SSMS, right-click each game database → Tasks → Back Up. Create a Full backup to a new dated file. Back up account, character, event, and ranking databases as a consistent set.
3. Copy matching configuration, scripts, and client patch. Label them with the same backup time and release.
4. Keep another copy outside the host. Confirm files exist and are readable; a file copy alone does not prove restoration works.

3. Rehearse a restore

1. On an isolated SQL instance, use Restore Database → Device to select each backup. Restore to new test database names and separate data/log paths, without overwriting live databases.
2. Point a separate DataServer configuration at the restored databases. Use private test ports and prevent the test from advertising to live players.
3. Start DataServer, ConnectServer, and GameServer. Log in and confirm restored character and inventory state.
4. Record the steps and time required. Fix any restore failure before relying on the backup for rollback.

4. Verify after deployment

• Services load from the correct working folders and register successfully.
• A clean client can list channels, log in, enter the world, and reconnect with saved state.
• Map transfers and changed features work on each relevant channel.
• No new repeating SQL, script, or configuration error appears. Disk space is sufficient for backups and logs.
• Rollback names the exact database backup and matching server/client files to restore.

Next action

Check Firewall rules before external testing. If restoration fails, open a support ticket with the SQL version, failed step, and exact error. Do not post player databases publicly.