
What to save before rolling back a Rust server
Keep a verified copy of the server as it is now before replacing anything. Even a broken world can contain usable plugin records, recent settings or evidence that helps you choose the right fix.
Keep one copy of the incident and one of the recovery point
If the wrong plugin ran at midday, your earlier backup might hold a working world and your current copy might still hold the staff changes made that afternoon. Store both. Use names that identify the server, the date and the reason for the copy, such as coast-before-rollback. Keep the incident copy out of any rotation that might remove it while you work.
- Keep the relevant console or plugin logs and note the active startup settings. Record the last time players saw the expected world or feature.
- Arrange the stop and pause automated starts. Once Rust and other writers have exited, capture the active identity, current config and any affected plugin or external data.
- Open the resulting copy somewhere separate. Check that it holds the files and recent changes you would need to go back. If you need it to be bootable, use a separate test server with its own ports and live integrations disabled.
Protect the chance to reverse course
If the disk is too full for a safety copy, use a separate destination or recover into a separate install first. If some files are unreadable, make a note of the gaps and keep the known good backup untouched.
Decide what would make you switch back
Set a check before the restore starts. For example, the protected area should still exist and a tester should be able to use its gate. When a restore recovers the area but leaves the gate broken, keep access closed and check the plugin separately while you still have both copies. Once players build again, reversing the restore also affects their new progress.