Back Up and Update a Rust Server Without Breaking Plugins

What a Rust backup must contain

The folder selected by +server.identity is the main recovery unit. It includes:

• the .sav world and .map file;
• player.* files including blueprints and state;
• sv.files, used by signs and related data;
• cfg/, including server.cfg, admins and bans;
• database -wal journals that belong to a consistent write set;
• oxide/ or carbon/, including plugins, config, language, data and permissions.

Also preserve the startup script or provider variables. Seed, world size, ports and identity may not live in server.cfg.

Create a consistent restore point

Update Rust, uMod/Oxide or Carbon

On a self-hosted server, update Steam app 258550:

steamcmd +force_install_dir /path/to/rust +login anonymous +app_update 258550 validate +quit

A provider's update button runs an equivalent action. Read its log and confirm the build actually changed.

SteamCMD returns binaries to vanilla. For uMod/Oxide, apply the build compatible with the new Rust version before starting. Carbon documents branch-aware self-updates; use production Carbon with public Rust and inspect the first boot. Do not pair a staging framework with the public game branch.

Validate before reopening

If Rust starts in vanilla, do not immediately add every plugin. Stop, verify the framework, then test plugins in small batches. If one blocks startup, preserve the message, disable it and find a compatible release instead of rolling back the whole server.

Restore after a failed update

1. Stop the server and archive the failed state so logs are preserved.
2. Identify whether the game, framework, plugin or world fails by testing an isolated copy.
3. For a complete restore, return identity, configuration and data from the same restore point together.
4. Do not downgrade a world already converted to a protocol unsupported by the old server. When clients require the update, fix the framework or plugin instead.
5. Validate with no players, then create a new archive once healthy.

The uMod/Oxide versus Carbon guide helps isolate the plugin layer. For an intentional reset, follow the Rust wipe guide so blueprints are not removed accidentally.

Frequently asked questions