Back Up a Sons of the Forest Dedicated Server
This guide walks you through backing up a dedicated Sons of the Forest server, whether you host it yourself or rent from a provider. You’ll learn exactly which files to copy, where they are, and how to restore them, so you never lose player progress, building structures, or server settings.
What You’ll Need
- Access to the server’s file system (via FTP, SFTP, or a hosting provider’s file manager).
- For self-hosted servers: the ability to stop the server process (or use the in-game console).
- Enough free disk space to store the backup (the save folder is usually a few hundred MB to several GB).
- An archive tool (e.g., 7-Zip, WinRAR, or built-in OS compression) if you want to compress the backup.
Step-by-Step
- Stop the server. The safest backup is made while the server is offline. If you’re using a hosting panel, click the “Stop” button. If self-hosted, send the
savecommand in the console, wait for the confirmation, then stop the process (Ctrl+C or close the window). For a live backup without stopping, you can skip this, but you risk a corrupted save if a write happens mid-copy. - Locate the save files. The default path for a dedicated server is:
steamapps/common/Sons of the Forest Dedicated Server/Saves/
Inside, you’ll find a folder namedMultiplayerand possiblySinglePlayer. TheMultiplayerfolder contains subfolders with long numeric IDs (Steam IDs) — these are individual worlds. - Identify the world to back up. Open each subfolder and check the
GameState.jsonfile (with a text editor) to see the world name. Alternatively, look at the folder’s modification date to find the one you’re using. - Copy the entire world folder. Do not copy individual files — the world is split across multiple files (e.g.,
GameState.json,SaveData.json,WorldState.json). Copy the whole folder to a temporary location on the same disk. - Compress the folder (optional but recommended). Right-click the copied folder and select “Compress” (or use 7-Zip). This reduces size and keeps all files together. Name it with a date, e.g.,
sotf_backup_2025-04-14.zip. - Move the backup off-site. Transfer the compressed archive to a different drive, a NAS, or cloud storage (Google Drive, Dropbox, etc.). This protects against hardware failure on the server.
- Restart the server. If you stopped it, start it again. Verify that players can connect and that the world loads correctly.
- Test your backup. At least once, restore the backup to a test directory (see Troubleshooting) to ensure it’s valid. A backup you never test is not a backup.
Common Mistakes
- Copying only one file. The world is split across multiple files; copying just
GameState.jsonwill not restore the world. - Backing up while the server is writing. This can produce a corrupted save. Always stop the server or use the
savecommand and wait for the confirmation. - Using the wrong folder. The
SinglePlayerfolder is for non-dedicated games. For a dedicated server, you need theMultiplayerfolder. - Not backing up the server config. The
ServerConfig.json(in the main server folder) contains your server name, password, and settings. If you lose it, you’ll have to reconfigure everything. - Keeping only one backup. If a save gets corrupted, you’ll need an older backup. Keep at least the last 3-5 backups.
Tips
- Automate backups. If you’re on Linux, use a cron job with
tarto create daily backups. On Windows, use Task Scheduler with a PowerShell script. - Use the in-game save command. On the server console, type
saveand wait for the “World Saved” message. This flushes all data to disk before you copy. - Name backups clearly. Include the date and a short note (e.g.,
pre-update_2025-04-14). This helps when rolling back after a patch. - Check the backup size. If the archive is suspiciously small (e.g., 1 KB), the copy likely failed. A typical world is at least 100 MB.
- Back up before any server update. Game patches can break saves. Take a fresh backup before updating the server.
Troubleshooting
- Backup fails to restore. If the world doesn’t load, you likely copied an incomplete folder. Check the archive for missing files. If you have an older backup, try that.
- Cannot find the Saves folder. If you’re using a hosting provider, the path may be different. Look for a file manager in your panel, or contact support. For self-hosted, search for
GameState.jsonon your server. - World loads but players lose items. This can happen if you restored an older backup. Make sure you’re restoring the latest valid backup.
- Permission errors when copying. On Linux, ensure the server user has read access to the Saves folder. Use
chmod -R +r Savesor run the copy as root. - Backup is corrupted (can’t open archive). The archive may have been interrupted. Re-create it, and verify the archive’s integrity (e.g., 7-Zip’s “Test” feature).
Frequently Asked Questions
How often should I back up my server?
At least once a day if the server is active. More frequently if you have many players or are doing major building projects.
Can I back up while the server is running?
Yes, but it’s risky. Use the save command first, then copy. However, a file could still be written during the copy, so stopping the server is the safest.
Where does the server store its config file?
The ServerConfig.json is in the root of the dedicated server folder, not in the Saves folder. Back it up separately.
Do I need to back up the entire server folder?
No. The essential data is in the Saves folder and the ServerConfig.json. The rest (game binaries) can be re-downloaded via Steam.
How do I restore a backup?
Stop the server, replace the contents of the world folder (e.g., Saves/Multiplayer/1234567890) with the files from your backup, then start the server. If you’re restoring to a fresh server, create the same folder structure first.
What if I don’t have FTP access?
Most hosting panels have a file manager. If not, contact your host. For self-hosted, you can use the server’s local file system directly.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.