Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
Back up the complete Rust server.identity directory for the instance, not just the map. That directory contains the .sav world save, .map terrain and monuments, configuration, player and server state, and other persistent files. If the server uses Oxide/uMod, also archive its data, configuration, and deployed plugins. A reliable backup is a consistent, dated copy that you can restore on a private instance before putting it back into production.
What a Rust server backup must contain
The value of a Rust backup is the complete server identity, because Rust stores more than terrain in that location. The +server.identity startup value selects the instance directory. If you back up a different directory, you may preserve the wrong server or only part of the state needed for recovery.
| Location or item | What it preserves | Why it matters |
|---|---|---|
server/<identity>/*.sav |
World data, entities, player buildings, deployables, and map state | This is the built and changing world players expect to return to. |
server/<identity>/*.map |
Terrain and monuments for the selected map | The save needs the matching map data to load the intended environment. |
server/<identity>/cfg/ |
server.cfg, administrator settings, bans, and related configuration |
It restores operational settings and access controls. |
| Player and server state files | Blueprints, deaths, identities, states, tokens, contact data, sign data, and other files present in the identity directory | These files can contain persistent player or server information that is not represented by the map alone. |
oxide/data/ |
JSON files used by plugins to persist their state | Plugin economies, permissions, progression, and other stored data can be lost if this directory is omitted. |
oxide/config/ and deployed plugins |
Plugin settings and the plugin binaries or source you deploy | Data files are useful only when the compatible plugins and their configuration are available. |
| Startup scripts and deployment notes | Identity, ports, map name, seed, size, custom command-line settings, and update steps | These details let you recreate the instance rather than guessing how it was launched. |
The .sav file is not a complete backup by itself
Rust creates backups when it saves, but the save file should be treated as one component of the identity directory. The .sav contains the changing world and its entities, including player constructions and deployables. The matching .map, configuration, state files, and identity name provide the surrounding context needed to start the same server.
The identity name is part of recoverability
Record the exact value used with +server.identity. Two instances on one machine can have different identities, and restoring files into the wrong one can make a valid backup appear to be missing. Keep the identity value beside the archive even if the directory name seems obvious.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Record the server before you copy it
A file archive is easier to use when it includes the settings that created the instance. Save the startup script or service definition and make a short text record containing:
- The
+server.identityvalue. - The Rust server build or update state.
- The map name, seed, and world size.
- Game, query, and any other configured ports.
- Custom command-line options and environment settings.
- Whether Oxide/uMod is installed, its build, and the plugins deployed.
Include server.cfg in the identity archive as well. The startup record and the configuration file serve different purposes: the startup settings determine how the process is launched, while server.cfg contains server configuration loaded by Rust.
How to create a consistent backup
Use a clean stop or a maintenance window in which no process can write to the files. Copying while the server is changing can produce a mixture of old and new files, so an archive that completes successfully is not necessarily a restorable snapshot.
- Announce the maintenance window. Tell players when the server will stop and record the intended wipe or recovery point.
- Stop the Rust process cleanly. Allow the server to finish its save and exit before copying. Do not begin by copying only the newest-looking file.
- Confirm the identity path. Match the directory selected by
+server.identitywith the instance you intend to protect. - Copy the entire identity directory. Preserve the
.sav,.map,cfgdirectory, player and server state, and any custom files under that identity. - Archive mod data separately when applicable. Copy the Oxide directory, especially
oxide/dataandoxide/config, together with the plugins you deploy. - Write recovery metadata. Put the identity name, map settings, Rust build, Oxide build, date, and wipe label in the archive name or in a companion text file.
- Move a copy off the server. Keep at least one archive on another disk, NAS, or backup service controlled by the operator. A backup left on the same machine does not help if that machine or its storage fails.
Stopping versus copying live
A stopped-server copy is the simplest way to obtain a consistent filesystem state. If you cannot stop the server, use a maintenance window where no writes occur and verify that the process is not changing the files during the copy. A live copy without write control can capture a save, configuration, or plugin JSON file halfway through an update.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Do not use a short filename allowlist
Oxide data files are JSON, but plugin authors can choose their own filenames. Copy the data directory rather than attempting to identify only a few familiar files. The same principle applies to the Rust identity: preserve the complete directory so an overlooked persistent file does not undermine the restore.
Backing up Oxide/uMod installations
Modded servers have two related but separate recovery sets. Rust’s identity directory restores the vanilla world and server state; Oxide/uMod supplies plugin code, settings, and persistent plugin data.
Include plugin state
Oxide documents oxide/data as the default location for JSON data used to persist plugin state. Depending on the plugins installed, that data can represent economies, permissions, progression, or other records that players and administrators expect to survive a restart. Restore it with the compatible plugin files instead of treating it as optional cache.
Include configuration and code
Archive oxide/config and the deployed plugin binaries or source. A data file without its plugin may be ignored, interpreted differently, or fail to load. Conversely, reinstalling a plugin without its data can create an apparently fresh state while the Rust world itself is intact.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Account for version-specific installation
Oxide installation is version-specific. Record the Oxide build and the plugin versions or deployment set used for each snapshot. After a Rust update, SteamCMD can leave the server files vanilla; a modded installation may need Oxide reapplied. Plan for that step during both routine updates and disaster recovery.
Choose a backup scope that matches the recovery target
| Recovery target | Required scope | Additional preparation |
|---|---|---|
| Undo a mistaken change on the same host | Complete Rust identity, including .sav, .map, cfg, and state files |
Keep the archived identity separate from the live directory until the restore is verified. |
| Move a vanilla server to a new host | Complete identity plus startup script and deployment notes | Install a compatible Rust build and recreate identity, map, seed, size, ports, and command-line settings. |
| Move a modded server | Vanilla scope plus oxide/data, oxide/config, and deployed plugins |
Install or reapply the compatible Oxide build after the Rust files are ready. |
| Investigate a restore before production | Any complete dated snapshot and its version metadata | Use a separate instance and private port so testing cannot alter the live world. |
The official documentation defines the files to preserve but does not prescribe a particular storage vendor, snapshot count, or retention period. Choose those policies according to how much progress your community can afford to lose and how much storage you control. Whatever schedule you choose, retain dated snapshots rather than replacing the only archive.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to label and retain snapshots
Use names that identify the instance and recovery context at a glance. A useful pattern includes the identity, date, wipe marker, Rust build, and Oxide build when present. For example, an archive name can contain the identity and an ISO-style date, while a companion text file records the map seed, size, ports, and exact versions.
- Keep the original identity name unchanged in the archive.
- Use a separate snapshot for each planned wipe or major configuration change.
- Store at least one copy away from the production machine.
- Protect archives from accidental overwrite while a restore is being investigated.
- Record whether a snapshot is vanilla or modded and list the plugins included.
Restoring a Rust server deliberately
Restoration is a staged operation. The goal is to load a known snapshot with compatible software, inspect it without exposing it to players, and only then replace production traffic.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
- Prepare the destination. Install or update a Rust server build compatible with the snapshot. Do not assume that the newest binary will load every older save or plugin combination without testing.
- Recreate the launch settings. Use the recorded
+server.identity, map name, seed, size, ports, and custom command-line options. Keep the test instance on a private or unused port. - Restore the identity directory. Place the archived identity, including the matching
.sav,.map,cfg, and state files, into the destination’s server storage. - Restore mod data if required. Reinstall or reapply the compatible Oxide build, then restore
oxide/data,oxide/config, and the deployed plugins. SteamCMD updates can return files to a vanilla state, so check the mod layer after every update. - Start privately and inspect logs. Confirm that the process loads the intended identity and map without errors before allowing public connections.
- Check the world and players. Visit known locations, verify buildings and deployables, inspect player state and blueprints, and confirm administrator and ban settings.
- Check plugin state. For a modded server, verify permissions, economies, progression, and any other plugin-owned records that matter to your community.
- Switch production only after validation. Stop the test process, apply the verified files to the production destination, and retain the pre-restore state in case the change must be reversed.
Moving to a new host
A host migration is not just a file upload. The destination must run the appropriate Rust build and reproduce the launch parameters. Ports, identity, map settings, and mod installation all affect whether the restored directory starts as the server you intended. Keep the old host untouched until the private validation succeeds.
Recovering after a SteamCMD update
SteamCMD updates keep server files vanilla. On an Oxide/uMod server, an update can therefore require Oxide to be reapplied before plugins and their data work again. Restore the Rust identity first, install the compatible mod layer, then check plugin configuration and data rather than assuming the update preserved them.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Saving a Rust world before a wipe
For a pre-wipe snapshot, follow the same consistency procedure as a disaster backup. Announce the cutoff, stop the server cleanly, copy the complete identity, archive Oxide data if used, and label the snapshot with the wipe date and version information. Do not delete or overwrite the archive until the new wipe has started successfully and the old world has been tested or intentionally retired.
The snapshot preserves the old world for later inspection or rollback; it does not automatically create a playable second server. To open it safely, restore it to a separate identity or test instance with an unused port, then verify that the map, buildings, player records, and plugins load as expected.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
Common backup failures and fixes
The world loads but buildings are missing
This usually indicates that the wrong .sav was restored, the save does not match the identity, or only map-related files were copied. Recheck the +server.identity value and restore the complete identity directory from one dated snapshot.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The terrain loads but the map is wrong
Confirm that the restored .map and the recorded map name, seed, and size belong together. A destination launched with different map settings can appear healthy while representing a different world.
Players or administrator settings are absent
Check the identity’s state files and cfg directory, including administrator and ban files. A map-only export cannot restore those records.
Plugins start with empty data
Restore oxide/data and oxide/config, then install the compatible plugin files. Because plugins may use different JSON filenames, copying only a handpicked list can omit required state.
The server becomes vanilla after an update
Reapply the compatible Oxide installation after the Rust files update, then restore or verify the plugin layer. Keep the Oxide build and plugin deployment notes with each snapshot so the process is repeatable.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The archive exists but cannot be trusted
An archive is not proven until it has been started on a disposable or private instance. Perform a restore test, inspect the world and state, and record the result. If the test fails, keep the failed snapshot for diagnosis but do not treat it as your recovery copy.
Restore-test checklist
- The intended identity starts and reports the expected map.
- The terrain, monuments, buildings, and deployables match the snapshot.
- Player state, blueprints, deaths, identities, and other retained records are present where expected.
server.cfg, administrator settings, and bans are loaded.- Ports and startup options are correct for the destination.
- Oxide/uMod loads when the snapshot is modded.
- Plugin configuration, permissions, economies, and persistent JSON data are present.
- The test ran on a private or unused port without changing production files.
Testing on a separate instance is the final control that turns a copied directory into a usable recovery plan. Keep the verified snapshot and its version notes together, and repeat the test after major Rust, Oxide, map, or plugin changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
