How to Back Up and Restore a Game Server (Saves, Configs and Mods)
On ChicagoServers, open your server's Backups tab, choose World and settings or Whole server, and click Back up now. To restore, click Restore next to the backup under Your backups. The principle behind it applies to any game: copy the world or save folder together with the config and mod folders, keep a copy somewhere that isn't the server itself, and label it with the date and game version.
The details that cause real data loss are small ones: copying while the game is mid-write, forgetting the config or mod files, restoring a world from a newer game version onto an older one, and never testing a backup until the day you need it. This guide covers each.
- Back up before every game update, mod change, config change and wipe, plus on a regular schedule.
- If in doubt, choose Whole server. At minimum: the world/save data, config files, admin and ban lists, and the mod or plugin folders with their configs (World and settings covers saves, configs and mods).
- Stop the server first (Stop saves the world properly), or use the game's own save-pause commands. A copy taken mid-save can be corrupt.
- A backup that has never been restored is a guess. Test one by unpacking it into a folder, or on a separate server or a spare copy.
- Keep at least one copy off the server: download the backups you can't afford to lose from the Backups tab.
On this page
When to take a backup
The scheduled backup covers accidents. The manual one before a risky change is what saves you from your own decisions. Take one:
- Before a game or server version update. Many games upgrade save data in place and can't go back. The PaperMC team's notes for Minecraft 26.1 call backups "absolutely mandatory" and warn that a world upgraded to 26.1 can't be downgraded.
- Before adding, removing or updating mods and plugins. A bad or outdated mod can stop a world from loading or damage what's in it, and the 7 Days to Die community wiki tells admins to update mods before loading a modded save.
- Before editing configs or changing world settings, so you can diff or roll back.
- Before a wipe or a map reset, if players might ever want the old map.
- On a schedule. Daily is a common baseline for active servers; weekly may be enough for a small private server that's online a few evenings a week. Use Automatic backups on the Backups tab, or add a Make a backup step to a task on the Schedules tab.
What files to include
Four kinds of data matter: the world or save itself, the server config, the admin/permission/ban lists, and the mods or plugins with their own configs. On the panel, World and settings covers saves, configs and mods, and Whole server backs up everything, the game files included. Paths vary by game and version, so if you copy files by hand, look in your server's files (on the Files tab or over SFTP) rather than trusting a generic list. These are common examples:
| Game | Back up | Notes |
|---|---|---|
| Minecraft (Java) | The world folder named by level-name in server.properties (the Server properties file on the Configs tab; default world), server.properties, whitelist.json, ops.json, and your plugins or mods folders including their configs | From 26.1 on, Paper keeps the Overworld, Nether and End under world/dimensions/minecraft/. Older versions used separate folders for each dimension, so back up the whole server directory and you can't miss one. |
| Valheim | The world data in the saves folder (worlds_local on current builds; older builds used .db and .fwl files), plus adminlist.txt, bannedlist.txt and permittedlist.txt | Iron Gate's server guide lists the default save paths. Player characters are stored on each player's own PC, not on the server. |
| Rust | The whole server/<identity>/ folder, including its cfg subfolder, plus the oxide or carbon folders if you run plugins | Map files (.map, .sav) and blueprint/player data (.db) all live in the identity folder. |
| 7 Days to Die | The whole Saves folder, your edited serverconfig.xml and the Mods folder | The community wiki recommends backing up the entire Saves folder before every update and recording which game version each world was created in. |
How to take a consistent backup
Games write to save files while they run. Copy a file mid-write and you can end up with a backup that looks complete but won't load. There are two safe approaches.
1. Stop the server first. Click Stop at the top of your server's page. Stop saves the world and shuts the game down properly. Then take the backup (or copy the files) and click Start again. It is the only method that works for every game, and for a world with a handful of players, a minute of downtime is usually acceptable.
2. Pause saving, if the game supports it. Minecraft Java Edition has console commands for this: save-off stops the server writing world files, and save-all flush writes everything pending to disk immediately. Copy the files, then re-enable saving. Type them on the Console tab and press Send; RCON is handled for you.
save-off
save-all flush
# ...copy the world and config files now...
save-onBedrock Edition has its own equivalent, save hold, save query and save resume, but it is more fiddly. For Bedrock and most other games, stopping the server is simpler and safer.
Whichever route you use, keep at least one copy somewhere off the server, for example a backup downloaded from the Backups tab. Add manual backups on top before risky changes.
How to back up on a ChicagoServers server
- Open the Backups tab
Sign in at panel.chicagoservers.co, open your server under Your servers, then the Backups tab. The tab is there when your plan includes backups.
- Stop the server if you want a guaranteed clean copy
Click Stop at the top of the page so nothing is writing to the save files. For a Minecraft server you can instead use the save-off sequence above on the Console tab.
- Choose what to back up
Under Back up now, choose World and settings (saves, configs, mods) or Whole server (everything, the game included), and add a note such as
2026-11-01 game-1.2.3 before update. Then click Back up now. You can leave the page while it runs. - Set up automatic backups
Under Automatic backups, choose How often, the time and what to back up, then click Save schedule. Times are Chicago time.
- Keep an off-server copy
Under Your backups, you can restore, download, delete or star each backup. Download the ones you can't afford to lose to your PC. Star a backup to keep it from being replaced.
- Or copy files by hand with the Files tab or SFTP
For a single folder, open the Files tab, right-click it and choose Compress to .zip, then Download. For big worlds use SFTP: copy Host, Port and Username from the blue SFTP bar (the password is your panel password) and set the client's protocol to SFTP, not plain FTP. Compare the folder size and file count with the original afterwards: a world that's 800 MB on the server and 40 MB on your PC didn't finish downloading.
- Start the server again
Click Start and watch the Console tab to confirm it loads the world normally.
How to restore a backup
- Pick the backup
On the Backups tab, under Your backups, click Restore next to the backup.
- Choose how to restore
Put it back stops the server, replaces its files, and starts it again if it was running. Unpack into a folder replaces nothing, so you can copy back just what you need. Leave Save the current files as a restore point first ticked so the restore can be undone, then click Restore. That keeps the broken data too, in case the backup turns out to be older than you thought.
- Match the game version
A save written by a newer version generally won't load on an older server. Restore onto the same or a newer version, and the same mod versions, than the backup was taken on. On Steam games, the Branch button on the update bar switches versions (make a backup first).
- Check the world name if you restored by hand
If you uploaded files from your PC through the Files tab or SFTP instead, put the world and config files back where they came from and make sure the world name matches the folder:
level-namein Minecraft's Server properties file, the World name field on the Startup tab in Valheim, or the Save folder field in Rust (the identity folder name). - Start and verify
Watch the Console tab for errors, join the server, and check something you know changed recently, such as a base or inventory. Only delete the old broken data once you're sure.
Test your backups and decide how long to keep them
Do a restore test once, now, while nothing is wrong: use Unpack into a folder on a recent backup to confirm it contains what you expect, or upload a backup to a spare server instance (or a temporary copy of the server) and confirm the world loads and the mods and permissions are there. If you ever change game versions, repeat it.
A simple retention routine that works for most community servers:
- Keep the last 7 daily backups.
- Keep one weekly backup for the last 4 to 8 weeks.
- Keep a labeled backup from before every major game update or modpack change until you're sure the update is stable. Star it on the Backups tab so it isn't replaced.
- Keep at least one copy away from the server, such as your own PC or cloud storage (use Download under Your backups). The usual 3-2-1 idea is three copies, on two kinds of storage, with one off-site.
Disk space is cheap compared to a lost world, but backups do add up. Let the automatic ones rotate and keep the labeled milestones by hand with a star.
Frequently asked questions
How often should I back up my game server?
Daily for an active server, weekly for a small private one, and always manually before updates, mod changes, config edits and wipes. The more your players would hate to lose a day of progress, the more often you should back up.
Can I back up a game server while it is running?
Only safely if the game lets you pause saving, as Minecraft Java does with save-off and save-all flush. Otherwise stop the server first (Stop on the panel saves the world), because files copied mid-write can be corrupt.
Why won't my restored world load?
The most common causes are a version mismatch (the backup is from a newer game version than the server), a world name that doesn't match the config or the Startup tab, missing mod or plugin files, or a backup taken while the server was mid-save.
Do I need to back up mods and plugins too?
Yes, or at least a list of exact mod versions and their config files. A world can fail to load or lose modded blocks and items if the mods that created it are missing or have different versions.