Create a Rust server backupWhat to back up and how to restore it

Published on August 9, 2026 · last updated on November 8, 2026

What needs to be backed up

The entire game state of a Rust server lives in the identity folder. Everything essential is in there:

• The save files with the map and all placed objects.
• The blueprint data of all players - see Wipe blueprints.
• Bans and other server-side lists.

On top of that come two things outside the folder: the server.cfg and - on a modded server - the plugin folder including its configuration files. The latter is easy to forget: a plugin configuration fine-tuned over months is often more work than the world itself.

Create a backup

1. Stop the server. A backup taken while the server is running can catch files in the middle of a write.
2. Connect via WebFTP or SFTP.
3. Download the identity folder, the server.cfg and, if applicable, the plugin folder.
4. Name it locally with the date, for example rust-2026-08-09.zip.
5. Start the server again.

If stopping is not an option, at least run server.save via the RCON console right before the download - then the state on disk is current.

When to back up

A Rust server gets wiped regularly anyway, so a daily backup rarely makes sense. These moments, on the other hand, do:

• Before every framework update - moving to new Oxide or Carbon versions after the force wipe is the most common cause of problems.
• Before installing new plugins or making larger configuration changes.
• Before switching to a custom map.
• At the end of a wipe cycle, if you want to keep the state as a memento.

In short: before every change that could keep the server from starting. What typically goes wrong then is covered in Server will not start.

Restore a backup

1. Stop the server.
2. Rename the current identity folder instead of deleting it - in case the backup turns out not to be the right one.
3. Upload the backed-up files to their original location.
4. Check folder and file names: the identity name has to match the one the server uses.
5. Start the server and watch the console.

Important: a world from an old Rust version cannot sensibly be continued after a force wipe - the update changes map generation. Backups protect you from mistakes; they are not a way back into a past wipe cycle.

What you do not need to back up

A complete Rust server folder is several gigabytes in size, and by far the largest part of it is replaceable. If you download everything, you wait a long time for an archive that consists ninety percent of files you can get again at any time:

• The game files themselves. A reinstall via the web interface brings them fresh and matching the current build anyway.
• The plain map file. It can be recreated identically from seed and worldsize at any time - back up those two numbers rather than the file generated from them. The save with all the bases, on the other hand, is unique and belongs in the backup.
• The framework files. Oxide and Carbon are installed at startup to match the game build. Restoring an old version does more harm than good.

What remains is a manageable package: the identity folder, server.cfg, users.cfg, plus the plugin folder, configurations and the data stored by the framework. That is small enough to grab quickly in between - and that is exactly what makes self-service backups actually happen instead of just being planned.

Check whether the backup is any good

A backup that is only put to the test in an emergency is a gamble. These three checks take two minutes and cover the most common mistakes:

1. Look at the file sizes. The save is by far the largest file in the identity folder. If it shows a suspiciously small number or zero bytes, the download was interrupted - usually unnoticed on an unstable connection.
2. Open the archive once. A ZIP that cannot be read locally will not be readable on the server either.
3. Compare the folder names. The identity name has to match exactly the one the server uses.

The third point is the most common failure when restoring and at the same time the least conspicuous: the server starts without any problem, just with an empty world, because it finds nothing under the expected name and generates a new map instead. If you then wipe a second time, the state is lost for good. That is exactly why the advice above says to rename the existing identity folder instead of deleting it. If the server does not start at all afterwards, Server will not start will help.

How many backups to keep

In practice, three backups are enough: the state before the last change, a current state from the running wipe cycle and an older one as a fallback. Anything beyond that is dead weight in Rust, because every save becomes worthless with the next force wipe anyway.

With configurations, it is the other way around. server.cfg, users.cfg and the plugin configs are tiny, but have grown over months - keep them permanently, ideally with the date in the file name and separate from the large save archive. Anyone who has once rebuilt a grown server configuration from memory after a slip will not make that mistake a second time.

A practical rhythm: the small configuration package whenever you have changed something significant, and the complete set once shortly before wipe day. That way, you are covered at exactly the two moments when, from experience, things go wrong in Rust.

Frequently asked questions