
How often should you back up a Rust server?
Set the schedule by how much progress players could reasonably lose. Take a separate backup before a major change so you have a nearby point to return to if that change fails.
Use the gap between successful backups
Imagine a building server that gets most of its play on weekend evenings. A daily backup at 06:00 UTC may leave Sunday's evening builds out of a recovery after a late crash. If you want to preserve that session, add a backup after the event or shorten the interval while the server is busy.
Check the capture time of the latest usable backup, including the latest one away from the host. A missed scheduled backup can double the gap you thought you had. If a backup failed, check the reason and make a working copy before depending on the schedule again.
Add a dated copy before a planned change
Take an extra copy immediately before a wipe, a new map or a plugin update that changes saved data. Record the change it precedes and verify the copy contains the files you would need to put back. For a change tied to both the world and a plugin database, consider a clean stop so both can be captured in one quiet window.
After the next busy week, check two things. Find a backup recent enough for a failure during play and find the particular backup you took before the last change. If frequent copies pushed the named copy out, keep important points separately from the daily rotation.