VEIN Server Save Management
VEIN worlds contain the group's progress, so backup is part of server setup rather than an emergency-only task. The active save location depends on the current package or provider; identify it before automating a copy.
Backup sequence
- Announce a maintenance window.
- Stop the server completely and confirm the process exited.
- Copy the complete active save/world directory and record build/time.
- Copy relevant configuration and package metadata.
- Start and perform a join/reconnect check.
Restore sequence
- Stop the server.
- Move the current failed copy aside; do not overwrite it.
- Restore a dated copy to the package's documented active location.
- Start a test instance or private server.
- Verify world, players, base, vehicles, and a new save before reopening.
Keep more than one checkpoint
| Checkpoint | Use |
|---|---|
| Before update | Rollback if the new branch or package fails. |
| Before admin/config change | Undo a bad setting or access edit. |
| After a healthy session | Known-good world with current build. |
Common mistakes
- Copying while the server is still writing.
- Backing up only a visible config file and not the world data.
- Restoring a save from a different branch without a test.
- Deleting the failed copy before proving the restore.
Related guides
Use managed VEIN hosting for panel-backed backups and restores.