# Should you stop a Rust server before taking a backup?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md)

Use your backup tool's running mode for routine copies if it handles the active save and databases. For a manual file copy or a change that needs the world and plugins to line up, plan a clean stop.

## Find out what changes while Rust runs

Rust keeps writing world saves and player data. A map save and a plugin database can change at different moments during the same copy. A file browser or archive tool copying one file after another can read files mid-write, even after the game reports a successful save. A running backup needs a way to take a completed save and handle the databases and plugin files it claims to cover.

| What you need to protect | What to do |
| --- | --- |
| Routine world recovery with a tool that handles live data | Use the tool's running backup workflow. Check that the completed copy includes the world save and the player or plugin data you rely on. |
| World and plugin state from the same quiet period | Warn players and stop Rust cleanly. Wait for every writer to finish, including any separate plugin service, then copy the files or use that service's export. |
| Files copied while the game crashed or was stuck | Keep the result as evidence. Check an earlier verified backup as your first recovery option. |

## Use a quiet copy before a coordinated change

Imagine a plugin that links shop listings to vending machines in the world. A sale can change the plugin's records while the game is still saving older vending machine state. Before replacing that plugin, announce a short stop, let Rust exit normally and make the backup while the writers are stopped. If the plugin uses an external service, follow its supported export procedure as part of that window.

Check the copy for the expected save and the shop's data. For a recovery check, use the same compatible plugin version in a separate test server with the shop connected to a test copy of its data. Keep production webhooks and any shared database disconnected. Confirm a known listing and its vending machine agree. That checks the relationship a file list alone misses.

## Sources

- [Facepunch guide to rotating Rust saves and databases](https://wiki.facepunch.com/rust/Getting-Started_w-Server)
- [SQLite documentation on backing up an active database](https://www.sqlite.org/backup.html)

## Related resources

- [Which SQLite files do you need when copying a Rust database?](https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/index.html.md)
- [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md)

---

HTML version: https://rustsc.com/learn/recovery/rust-backup-running-or-stopped/
