Rust Server Backup and Restore Guide 2026

Published on | Updated

Which Rust server files to back up, how to take a clean copy, how panel backups work, and how to restore a world, one plugin or a whole server without losing player data.

Rust

A Rust backup that you can actually restore has two parts: the server's identity folder, server/<identity>/, with the map, the save, the player databases and cfg/, and the oxide folder with your plugins, their configs and their data. Take it with the server stopped, keep a copy somewhere other than the server, and know which file brings back what. The game files themselves you never need to back up, because SteamCMD reinstalls them.

Everything below was checked on 25 October 2026 against Facepunch's wiki, the Oxide and Carbon docs and our own plans.

What to back up

The identity folder

Everything Rust keeps for one server lives in server/<identity>/, where the name comes from server.identity. Facepunch's wiki page on that folder lists what each file holds:

File or folderWhat it holdsBack it up?
*.mapThe map: terrain, monuments. Procedural maps are named proceduralmap.SIZE.SEED.mapYes
*.sav"all map data and entities, player buildings, deployables and more"Yes
player.blueprintsYour players' blueprintsYes
player.deaths, player.statesWho killed a player and why, death markers, the hostile timerYes
player.identitiesNot explained on the wikiYes
player.tokensRust+ pairing. Without it, players have to pair againYes
sv.filesSigns and picturesYes
companion.idYour server's Rust+ identifierYes
cfg/server.cfg, users.cfg with your admins, and bansYes
loadouts/, serveremoji/Saved loadouts and custom emojisIf you use them

The database files (.db) can have a -wal file next to them. Copy those too; the next section explains why.

The oxide folder

FolderWhat it holds
oxide/pluginsThe plugin .cs files
oxide/configPlugin configs, one JSON file per plugin
oxide/dataPlugin data, plus Oxide's own permission data
oxide/langPlugin messages, including any you translated or edited
oxide/logsLogs. Useful after a crash, not needed for a restore

Oxide's data files guide is clear on this: "When making server backups, it's crucial to include the oxide/data/ directory." Its permissions guide adds that permissions are stored in the oxide.users and oxide.groups files, and that oxide.export writes them out as JSON, "useful for backup purposes or transferring permission settings between servers."

If a plugin keeps its data in an external MySQL database, that data is not in these folders. Back up the database separately.

What you can skip

RustDedicated_Data, steamapps and the server binaries come back with a SteamCMD install of app 258550. Do not restore old Oxide files onto a newer Rust build either. Oxide's install guide says "Don't mismatch version of Oxide and version of servers", so after a restore you install the Oxide release made for the Rust build you are running.

Take the backup with the server stopped

Two things make a copy of a running Rust server unreliable.

The databases. Facepunch's wiki says "Rust uses a journaling technique with its database(db) files. This is the reason you will see a -wal file with those." SQLite, the database format behind it, explains on its WAL page what that means for copies: "The WAL file is part of the persistent state of the database and should be kept with the database if the database is copied or moved. If a database file is separated from its WAL file, then transactions that were previously committed to the database might be lost, or the database file might become corrupted."

The save. The .sav file is written at each autosave. Carbon's Rust convar reference lists server.saveinterval with a default of 600 seconds, so a copy of a running server can miss up to ten minutes of building.

The routine that avoids both:

  1. Warn your players with say "Server restarts in 5 minutes for a backup".
  2. Run server.save.
  3. Stop the server from the panel, or with quit in the console. Stopping also unloads the plugins, and some plugins write their files when they unload.
  4. Make the backup.
  5. Start the server again.

Rust's own save copies are not a backup

According to the wiki, the server "creates and keeps backups every time the server saves". The Carbon reference lists server.savebackupcount with a default of 2. Those copies sit in the same folder as the save and roll over at every autosave, so they only reach back a few saves, and a wipe routine that deletes the old save files deletes them too. They can help after a bad shutdown. They do not replace a backup you keep elsewhere.

Backups on our panel

Our Rust plans include backup slots in the game panel: 2 on STONE and METAL, 3 on SULFUR, FUEL, BUILDING PLAN and HAMMER (shop pages, 25 October 2026). You make these backups yourself in the panel's Backups tab. At checkout there are two optional add-ons:

  • Automatic Off-Site Backups, €5.00 a month: "Daily backups stored off-site, restore them from the game panel."
  • Extra backup slots, €6.50 a month: "Five extra backup slots in the game panel."

The panel is Pterodactyl. Its standard backup dialog has three fields worth knowing:

  • Backup name. Use the date and the reason, such as 2026-11-05 before update.
  • Ignored Files & Directories. Files and folders to leave out, with wildcards. Left empty, the panel uses a .pteroignore file in the server's root folder if there is one.
  • Locked. "Prevents this backup from being deleted until explicitly unlocked."

Each backup can be downloaded, restored, locked or deleted. With 2 slots, a pattern that works: keep one locked backup from right after your last good update, and use the other for the backup before each risky change. Download the important ones as well, or copy the identity and oxide folders to your own computer over SFTP, so one copy never lives on the server.

Restoring: use the smallest restore that fixes the problem

One plugin's config or data

When a plugin's config or data file is damaged or a change went wrong, there is no reason to roll back the world.

  1. oxide.unload PluginName
  2. Replace the file in oxide/config or oxide/data with the copy from your backup.
  3. oxide.load PluginName

Unload first. Oxide's config guide warns that some plugins save their configuration when they unload, so a config you replaced while the plugin was running can be overwritten. Use the same order for data files.

The world

To roll back the map, for example after an admin mistake or a plugin that spawned something it should not have:

  1. Stop the server.
  2. Put the .sav file from the backup back in the identity folder, with the .map file if you use a custom map or changed the map since.
  3. Keep server.identity, server.seed and server.worldsize (or server.levelurl for a custom map) exactly as they were when the backup was made.
  4. Start the server and join to check your bases.

Step 3 matters because of how Rust finds its save. The game builds the save file name from the current map, and if no file with that name exists it starts a new map. You can see this in the game code quoted on Oxide's OnNewSave page: when the file is missing, the console prints a warning that starts with Couldn't load. If you see that after a restore, the name does not match. Check the seed, the size and the identity before you let anyone build on the fresh map.

Then decide about the player databases. Restore only the .sav and players keep the blueprints they learned since the backup. Restore player.blueprints as well and they lose those too. If you restore a database file, restore its -wal file from the same backup with it, and do not leave the current -wal next to an older database file.

After a forced wipe

A save from before the monthly forced wipe cannot be brought back on the new build. The wiki explains that the number in the save's file name "increases at a forced wipe forcing your server to create a new one and not use the old", and that "It is dangerous and ill-advised to just rename an old sav in an attempt to circumvent the forced wipe." Restore world backups within the same build. Plugin data from before the wipe is a different matter: you can restore it if you decide to keep, say, economy balances.

The whole server

After a failed update, or when you move a server:

  1. Make sure the game files are on the current Rust build and that Oxide is the release for that build.
  2. Restore the identity folder and the oxide folder.
  3. Use the same server.identity name and the same startup settings as before.
  4. Start, read the console, join and check.

Restoring a panel backup brings back everything that was in it. Pterodactyl stops the server first ("Your server will be stopped") and offers a checkbox, "Delete all files before restoring backup." Tick it when you want the server exactly as it was at the time of the backup. Leave it unticked to lay the backup over the current files, which keeps any file the backup does not contain. If the backup was made before a mandatory update, it holds the old game files and the old Oxide build, so update the server and install the matching Oxide build again before you open.

If you are moving a Rust server to us from another host, the €15.00 one-time migration add-on at checkout means "We move your existing server and files to Space-Node for you."

Test a restore before you need one

A backup you have never restored is a guess. Restore your latest backup onto a test server or a second identity once, start it, and check that the console does not print the Couldn't load warning, that your bases are there and that your plugins load with their data. Our staging branch post explains how to set up a test server on the public branch; it doubles as a place to test plugin updates.

When to back up

  • Before every update night. The monthly update and forced wipe come on the first Thursday at 19:00 London time; our Halloween update checklist has the expected November date and the time in eight zones.
  • Before you update, add or remove plugins. Our plugin update guide covers the update order on wipe night.
  • Before you edit data files by hand or change the map.
  • Before your own wipes. The wipe day checklist covers which files a map wipe and a blueprint wipe delete.

Rust hosting with us

Our Rust server hosting plans come with panel backups you make yourself, 2 slots on STONE and METAL and 3 on the bigger plans, plus file access over SFTP for your own copies. Daily off-site backups are an optional add-on for €5.00 a month. STONE starts at €10.20 a month with 8 GB RAM, and the plans are set up for Oxide. If you run Carbon, ask in live chat first; Carbon keeps plugin data under carbon/ instead of oxide/, with configs in carbon/configs (porting guide).

Support is online from 08:00 to 20:00 UTC every day, by live chat, Discord and email.

FAQ

Where are Rust server save files stored? In server/<identity>/, where the identity is set by server.identity. The world is in the .sav file next to the .map file, and player data is in the player.* database files in the same folder.

Does a Rust wipe delete blueprints? A forced wipe gives the save a new number, so the server starts a fresh map. According to Facepunch's wiki this usually only affects the save file; for a blueprint wipe you delete the blueprints file yourself, unless Facepunch announces a forced blueprint wipe.

Can I restore my Rust server after a forced wipe? Not the old world on the new build. The wiki calls renaming an old save to get around a forced wipe "dangerous and ill-advised". Plugin data and configs from before the wipe can be restored.

Are backups automatic on Space-Node? Panel backups are ones you make yourself, in 2 or 3 slots depending on the plan. Daily off-site backups are an optional add-on for €5.00 a month.