Back up and restore a Conan Exiles server

Identify the active world

ConanSandbox/Saved contains the installation's saves and configuration. Funcom identifies game.db for Legacy Exiled Lands and dlc_siptah.db for Legacy Siptah. Enhanced uses distinct converted data. Locate the files actually used by the instance instead of assuming a Legacy filename applies.

Record the map, game version, mods and load order. Hosting panels may expose several backups, so confirm which belongs to the active server.

Create a consistent archive

Notify players and stop the server cleanly. Wait for the process to exit before downloading ConanSandbox/Saved with its full structure. Also retain mods or, at minimum, the publications, versions and settings needed to reconstruct the setup.

Verify transfer completion and keep a copy outside the hosting account. Label it with date, edition and world. Copying while the database is writing may produce an inconsistent archive. Use a shutdown for manual copies or a documented managed backup process.

Restore without losing the current state

Export the current state first, even if it is faulty, then stop the instance. Restore the chosen backup with compatible configuration. Verify paths, selected map and mods before starting.

If the incident followed an Enhanced migration, returning to Legacy requires the original Legacy archive and a compatible installation. A converted save does not replace that archive. Likewise, loading a world without required mods can affect dependent content.

Validate with players

Check characters, clans, buildings, inventories, storage and important followers. Verify damage and decay rules before reopening to the group. Finish with a save-and-restart cycle.

If something is missing, avoid accumulating further changes while investigating. Compare the restoration timestamp with logs. A technically successful recovery may simply predate the missing construction.

Frequently asked questions