Overview
Corrupted world saves, accidental wipes, or bad plugin configs can wipe out hundreds of player base hours. Implementing regular backup checkpoints ensures quick recovery without data loss.
Critical Files to Protect
When creating backups, the following files represent all persistent server data:
| Path | Purpose |
|---|---|
/server/<identity>/*.sav |
World save files: bases, deployables, inventories |
/server/<identity>/player.blueprints.*.db |
Player tech-tree research progression |
/server/<identity>/cfg/users.cfg |
Admin and moderator authorization list |
/server/<identity>/cfg/bans.cfg |
Player ban records |
/server/<identity>/cfg/server.cfg |
Server identity and gameplay settings |
/oxide/ or /carbon/ |
Modding configs, plugin files, and permissions |
Creating Backups in DustBowl Warden
Automated Scheduled Backups
- Navigate to the Backups tab in DustBowl Warden.
- To create a manual snapshot, click Create Backup.
- Give it a descriptive name (for example:
Pre-Patch Friday Backup). - You can also automate daily snapshots via the Schedules tab using the Create Backup schedule task.
Manual Save via Console Checkpoint
Before restarting or updating server files, always force a database flush to disk by running:
server.save
Wait for the console to output Saving complete before initiating a server restart or shutdown.
Restoring a Previous Save
If a map file becomes corrupted or you wish to roll back after a griefing incident:
- Stop your server from the Warden Console.
- Navigate to the Backups tab.
- Locate your desired restore point.
- Click the three dots
...next to the backup entry and select Restore. - Confirm the action. Warden will unpack the snapshot into the container directory.
- Start the server. The engine will read the restored
.savcheckpoint.
Next Steps
- Review common fixes in Rust Server Troubleshooting and Common Crash Fixes.
- Learn setup fundamentals in How to Set Up a Rust Dedicated Server.