Restarting a Satisfactory dedicated server safely prevents corrupted saves and lost progress. This guide walks you through the proper shutdown, backup, and restart procedure, ensuring your factory and friends’ work remain intact.
What You’ll Need
- Access to the server’s command console (either through the hosting provider’s panel or a terminal).
- File access to the server’s save directory (via FTP, SFTP, or the host’s file manager).
- Enough free disk space to store a backup of the save files.
Step-by-Step
- Notify players. Announce the restart in chat or on your community channel at least 10 minutes in advance. Ask them to finish current tasks and log off.
- Save the game manually. In the server console, type
saveand press Enter. Wait for the confirmation message that the save was written successfully. This ensures all recent changes are stored. - Stop the server gracefully. In the console, type
stopand press Enter. This triggers a clean shutdown, which flushes all data to disk. Do not force-kill the process unless absolutely necessary. - Wait for the process to exit. Watch the console until you see a message indicating the server has fully stopped. This may take a few seconds.
- Back up the save files. Navigate to the server’s save directory (usually
saves/inside the server folder). Copy the entiresavesfolder to a safe location on your local machine or a separate backup drive. This is your safety net if anything goes wrong during the restart. - Apply updates or config changes (optional). If you’re restarting to install a game update or change server settings (like in
Game.ini), do that now while the server is offline. - Start the server. Launch the server using your normal method (start script, systemd service, or hosting panel). Wait for it to fully load the world and appear in the server list.
- Verify the save loaded correctly. Check the console logs for any errors related to loading the save. If players log in and report missing structures or progress, you may need to restore from the backup.
Common Mistakes
- Force-killing the process. Using
killor closing the terminal window without the gracefulstopcommand can corrupt the save file. - Skipping the manual save. Relying only on the autosave can lose up to a few minutes of progress if the autosave interval is long.
- Not backing up before updates. Game updates occasionally introduce bugs that can damage saves. A backup lets you roll back.
- Starting the server before the old process fully exits. This can cause port conflicts or file locks.
- Restarting while players are still connected. Players may lose unsaved progress or experience crashes.
Tips
- Set up a regular automatic backup schedule (e.g., daily) to minimize data loss in case of unexpected crashes.
- Keep multiple backup versions, not just the latest. If a corruption is not noticed immediately, older backups can be lifesavers.
- Use a script to automate the backup step, copying the save folder with a timestamp.
- If you’re using a hosting provider, check if they offer snapshots or automatic backups as part of the service.
- Test your backup restoration process occasionally to ensure you know how to do it when needed.
Troubleshooting
Server won’t start after restart. Check the console logs for errors. Common causes: missing or corrupted save file, port already in use, or insufficient disk space. If the save is corrupted, restore from your backup and try again.
Players report lost progress. If you skipped the manual save, the autosave might be the most recent. If that’s also missing, you’ll need to restore from a backup. Always inform players to check their last session time.
Server starts but the world is empty. This usually means the server loaded a fresh world instead of your save. Verify the correct save file is specified in the server config and that the file exists in the saves folder.
Console shows “Save failed” when you type save. This often indicates a disk space or permissions issue. Free up space or fix folder permissions before proceeding.
Frequently Asked Questions
Do I need to restart the server after every update?
Yes, most updates require a restart to apply. The server will typically not run the new version until it is restarted.
How often should I back up my server?
At least daily, or more frequently if you have active players. Some hosts offer automatic backups; enable them if available.
Can I restart the server without stopping players?
No. A restart requires stopping the server process, which disconnects all players. You can schedule it during low-activity hours.
What is the difference between a graceful stop and a force kill?
A graceful stop (stop command) allows the server to save and close files properly. A force kill (e.g., kill command) cuts off power abruptly, risking file corruption.
Where are the save files located?
Typically in the saves folder inside the server installation directory. The exact path may vary by hosting provider.
What should I do if the server crashes during a restart?
Wait a few seconds, then try starting it again. If it fails, check the logs and restore from the most recent backup if necessary.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Tongue Escape Codes: What They Are0.20 movements/s
- Claude Code Workflow Habits Worth Trying
- HDMI 2.1 Explained: Why It Matters for Gaming
- Veeam Plugin for VMware Cloud Director: How It Works
- Best Path of Titans Server Hosting: Top Picks
- Oppo First Foldable: 120Hz Display & Snapdragon 888