How to Back Up and Restore a SCUM Server
SCUM keeps its whole world in one SQLite database. Which files to copy, why the -wal and -shm files matter, what the server’s own .db-backup copies are good for, how to restore without landing on an empty world, and how to wipe safely.
One database, three files that belong together
Most survival games save the world as a pile of separate files. SCUM does not. Characters and their progress, bases, vehicles and the world itself all live in a single database, and the server writes to it constantly while it runs. That makes backups simpler in one way, because there is only one save to look after, and riskier in another, because a careless copy can catch the database halfway through a write.
- Stop the server before copying
- Move the three files together
- Never leave an old -wal next to a restored database
- Keep Config/WindowsServer with it
The two extra files are part of how SQLite works. The -wal file holds recent changes that have not yet been merged into SCUM.db, and -shm is the index that goes with it. Copy SCUM.db on its own from a running server and you can miss those changes or end up with a database that will not open. Restore a database but leave an old -wal behind, and the server can apply those stale changes on top of the world you just uploaded.
What else to keep
| Folder | What is in it | Back it up? |
|---|---|---|
SCUM/Saved/SaveFiles/ | SCUM.db, SCUM.db-wal, SCUM.db-shm and the server’s own .db-backup copies | Yes, every file |
SCUM/Saved/Config/WindowsServer/ | ServerSettings.ini, AdminUsers.ini, ServerSettingsAdminUsers.ini, BannedUsers.ini, WhitelistedUsers.ini, ExclusiveUsers.ini, SilencedUsers.ini, EconomyOverride.json, RaidTimes.json | Yes: your rules, admins, bans and economy |
SCUM/Saved/Logs/ | Server logs | Only if you need them, for example for a Discord bot’s history |
| Server install folder | The game files themselves | No, Steam downloads them again |
The simplest rule is to copy the whole SCUM/Saved folder. It holds the world and every setting, without the game files, so it stays a manageable size.
Back up a SCUM server step by step
- Warn your players and pick a quiet moment. SCUM writes changes to the database as it goes, so a clean stop loses very little, but nobody likes being kicked mid-fight.
- Stop the server from your panel and wait until it is fully offline.
- Download
SCUM/Saved, or at least everything inSaveFilesandConfig/WindowsServer, through your host’s file manager or FTP. - Label it. Put it in a folder named with the date and the reason, such as
2026-11-18 before wipe, on your own PC or in cloud storage. - Start the server again.
If you run the server yourself and want copies without stopping it, SQLite’s own .backup command, run with the sqlite3 tool against SCUM.db, takes a consistent copy of a live database. A plain file copy of a running server does not.
The copies SCUM makes for you
Look in SaveFiles and you will usually find one or more files named like SCUM_XXXXX.db-backup. The server writes a copy of its database there when it starts, and hosts report that it keeps only the few most recent. They are handy for undoing a mistake from the last restart or two. They are not a backup plan: they sit on the same disk as the live world, they are replaced every time the server restarts, and a server that restarts every few hours can cycle through all of them within a day.
Many hosts add scheduled panel backups on top. Check how often they run, how many they keep, and that they include SaveFiles, then download one now and then so a copy exists away from the host. Our game server backups explainer covers how often to schedule them.
Restore a backup
- Stop the server.
- Rename the current
SCUM/Savedfolder, for example toSaved.broken, so you can go back if needed. - Put your backup in its place. Check the result: the database must sit at
SCUM/Saved/SaveFiles/SCUM.db, not one folder deeper. An upload that lands in an extra folder is the most common mistake, and the server then starts on an empty world. - If your backup has no
SCUM.db-wal, make sure no-walor-shmfile is left inSaveFiles. If it has one, keep all three together. - Start the server and check your base and a character in game before letting everyone back in.
To restore just the world and keep today’s settings, replace only the files in SaveFiles. To roll back to one of the server’s own copies, stop the server, move SCUM.db, SCUM.db-wal and SCUM.db-shm out of the folder, rename the .db-backup file you want to SCUM.db, and start the server.
Wipes: back up first, then switch it off again
Wipes are set in ServerSettings.ini with three switches: scum.PartialWipe, scum.GoldWipe and scum.FullWipe. Switches in that file take True or False, rather than 1 or 0 as they did before December 2025. Each one makes the server wipe the next time it starts, and a wipe can only be undone from a backup.
The trap is that the switch stays on. If you leave scum.FullWipe=True after the wipe, the server wipes again at every start, including the automatic restarts many hosts schedule. Take a backup, set the switch, restart once, then set it back to False straight away.
Moving to a new host
Moving a SCUM server is a backup on one machine and a restore on another. Download SCUM/Saved from the old server, upload it to the same place on the new one, and start it. Players keep their prisoners, because each one is stored in the database under the player’s SteamID64, so it moves with SCUM.db. Run the same game version on both sides, and keep your old server until you have checked the new one. Our guide to moving to a new host covers the rest of the switch, and the SCUM server requirements guide helps you pick the right plan size.
A single-player world is a different matter. Single player also uses a SCUM.db, but there is no official way to move it to a dedicated server, and because world and characters share one database, you cannot lift out just your character.
Many SCUM hosts run scheduled backups and let you restore from the panel. Compare UK hosts, and what each one includes, in our roundup.
Compare the best SCUM server hostsSCUM server backup FAQ
Where is the SCUM server save file?
In SCUM/Saved/SaveFiles/SCUM.db. It is one SQLite database holding the world and every player, with two companion files, SCUM.db-wal and SCUM.db-shm.
Can I back up a SCUM server while it is running?
Not with a plain file copy, which can catch the database mid-write. Stop the server first, or use SQLite’s .backup command, which takes a consistent copy of a live database.
What is the .db-backup file in SaveFiles?
A copy of the database the server makes when it starts. Rename it to SCUM.db, after moving the current database files out, to roll back to that point.
Does a SCUM wipe delete my backups?
A wipe resets the live world, and the server’s own copies are replaced on the following restarts. Download a backup before you set any wipe switch.
Can I move my single-player SCUM world to a server?
There is no official way. Single player uses its own SCUM.db, and world and character data share that one database, so they cannot be split.
More SCUM server help
Compare hosts and size your server.
SCUM updates and host panels change. Where your server or your host’s panel works differently from what is described here, follow what you see on your server.
