Skip to main content

Which Rust server backup should you restore after an incident?

Choose the newest compatible backup that still contains the state you want. Work out when the damage started, then check what the closest copies actually contain.

Start the timeline where things changed

Separate the first report from the first bad change. If players report missing deployables at 21:00 UTC, a staff note about a plugin change at 20:10 UTC is a better starting point for the search. Compare staff messages, console history and backup times using the same time zone. Include the last time someone saw the data intact.

A backup's end time can be later than the save it contains. A copy that finished at 20:20 UTC might hold the world saved at 20:00 UTC and plugin files captured after 20:10 UTC. Look for the associated save time and check the specific data you need. When the times are uncertain, compare the closest usable copies from either side.

Choose between two close candidates

Suppose the 19:55 UTC backup has the missing deployables and the 20:20 UTC copy already shows empty foundations. For a world rollback, the 19:55 UTC point is the better candidate. If the loss turns out to be a vanished plugin menu with the world intact, check whether you can recover its settings or data independently so players can keep their later world progress.

  1. Preserve the current server and its logs separately so you can compare both states after a restore.
  2. Check the candidate against the active map and game version. Use the linked test-restore guide to boot a separate copy with its own ports and live integrations disabled. Verify the missing feature or a known landmark.
  3. Tell players which point you verified and which play time it could replace. After restoring, check the same spot on the server before reopening it.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details