
Which files belong in a Rust server backup?
Start with what you need back. A playable world, learned blueprints, staff permissions and plugin progress can each depend on different files. Keep the list beside the backup so you can check it after an update or a move.
Match the files to what players will notice
Find the active game install and Rust server identity. For shared installs, check you have the folder for the right server. Confirm the actual locations on your host because frameworks and plugins can use other folders or external services.
| What to recover | What to include |
|---|---|
| Terrain and built world | The matching .map and .sav. Keep the original custom map download or record the procedural map settings. |
| Learned blueprints and other player state | The corresponding player databases and any matching database side files from that capture. |
| Server rules and access | The active identity's cfg folder and a private copy of the startup settings the host uses. |
| Modded features and progress | Framework settings and permissions, required plugin versions, configuration, data and any supported export from an external service. |
Follow one feature from files to in-game behavior
On a server with a tournament arena, a world copy might contain the course while the scoreboard lives in a plugin database. Open a recent backup in a separate folder and find the plugin's data alongside the world files. If the scores live in an external database, record how to restore the matching export and who can access it.
Check the inventory after adding a feature that saves progress. For the arena, check that you can recover the course, the spawn settings and a known score. Update the list if any of those depend on files or settings outside the original backup.