Empyrion Dedicated-Server Save Backup and Restore
Empyrion saves are more than one file. A galaxy has a named save directory, shared entity data and a scenario relationship. A partial copy can produce a server that starts while bases, ships or the intended world appear to be missing.
What to back up
| Item | Why it matters |
|---|---|
Saves/Games/<GameName> | World state, structures, players and shared entities. |
The active dedicated.yaml | Maps the server to the intended save and scenario. |
| The scenario folder | Supplies the playfield and configuration content used by the save. |
| Logs before a failed restore | Shows whether the server loaded the expected world or created a new one. |
Safe restore sequence
- Stop the server cleanly and wait for the process to exit.
- Make a copy of the current state before replacing anything.
- Restore the complete named save directory, not only the visible player files.
- Restore the matching scenario version and keep the same scenario folder name.
- Confirm
GameNameindedicated.yaml, then start once for an admin-only test.
Never test a restore over the only copy of a long-running galaxy. Keep the pre-restore directory until a player can see the expected bases, faction data and ships.
Supercraft plans provide managed save handling and backups; see Empyrion server hosting. For scenario version discipline, use the Reforged Eden 2 guide.