Menu
  Log out
 

Necesse Server Backup & Restore Guide

Necesse Guide • Updated Aug 29, 2026

Necesse Server Backups and Restoring Saves

Necesse stores a world as a compressed archive by default. Back up the active world archive and server configuration before updates, world-setting edits, or destructive admin commands.

Default save locations

PlatformServer configWorld saves
Linux~/.config/Necesse/cfg/server.cfg~/.config/Necesse/saves/
Windows%APPDATA%\Necesse\cfg\server.cfg%APPDATA%\Necesse\saves\

A -datadir or -localdir launch option can change these paths. Confirm the active command before copying.

What is inside a world save?

World saves are named <WorldName>.zip and contain the world data, including worldSettings.cfg. Keep the original archive untouched. If you need to edit the world settings, copy it, extract the copy, make the change, and re-create the archive in the format the current server expects.

Manual backup

  1. Use /save if you have moderator permission, then stop the server cleanly.
  2. Copy the world archive from the active saves directory.
  3. Copy server.cfg and record the launch command, world name, and build.
  4. Store the backup outside the server's disk or provider account.
  5. Use a dated filename and keep more than one restore point.
# Linux example
cp ~/.config/Necesse/saves/MyWorld.zip /srv/backups/necesse/MyWorld-2026-08-29.zip
cp ~/.config/Necesse/cfg/server.cfg /srv/backups/necesse/server-2026-08-29.cfg

Hosted backups

Check whether the provider backs up the compressed world archive, configuration, and logs; how long it retains copies; and whether you can download and restore them. “Daily backup” is not enough unless the restore point is identifiable and tested.

Restore a world

  1. Stop the server and rename or copy the current world archive; do not delete it yet.
  2. Put the chosen dated archive in the active saves directory.
  3. Confirm the launch command's -world name matches the archive.
  4. Restore the matching server.cfg only if the configuration is also part of the rollback.
  5. Start privately, inspect logs, join with a test account, and verify the settlement before inviting players.

Backup policy for a long-running colony

  • Keep the latest daily copy while the world is active.
  • Keep a pre-update and pre-experiment copy.
  • Keep one copy off the server machine.
  • Test a restore to a separate directory periodically.

Related guides

Want managed backups for your settlement? Host Necesse with Supercraft.

Tired of fighting this issue every patch?

Run a managed Necesse server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Necesse hosting plans →
← Back to Necesse Guides
Top