Guides→Backups & restore
Backups & restoreLaunch-required workflow

Create, export and restore backups

Create recovery points before risky changes, keep production backups away from the game node and treat restore as a destructive action.

When to create a manual backup

  1. Before changing game versions or server types.
  2. Before installing or updating a large modpack or plugin set.
  3. Before importing or replacing a world.
  4. Before a destructive repair, reinstall or future game-switch workflow.

Automatic backups

Runic’s production design sends automatic recovery copies to independent S3-compatible storage instead of keeping every backup beside the game workload on the same node.

Exact automatic frequency, retention and export limits are published only after production restore testing and storage economics are finalized.

Restore safely

  1. Confirm the backup timestamp and the world/config state you expect it to contain.
  2. Stop the server when the restore workflow requires it.
  3. Confirm the destructive restore action explicitly.
  4. Start the server and verify the world, configuration and required packages before deleting newer recovery points.