Game backups
Use a server’s Backups tab to create, download, restore, or delete snapshots.
The overview’s recent backups and the main Backups page list only archives
from servers where you have server.backups.read permission.
Storage indicators distinguish local archives on Spark from off-host S3 copies.
Creating, restoring, downloading, and deleting backups require separate grants;
backup policy requires server.configure. See
Accounts and access for the
permissions and Backup maintainer preset.
Choose a backup type
| Type | Contents |
|---|---|
| Full server | The whole game-data directory |
| Save data only | Files and folders declared by the Ember’s savedata_paths |
Choose the type for each manual backup or backup schedule; there is no server-wide default. Save-data backups require the latest Ember to declare save paths. Pending server-value reviews do not block either type. Path changes apply to new backup requests immediately, without deployment sync or restart.
Create a backup
Backups can run while the server is running. Live backups copy files as they are read; they do not flush in-memory game saves or provide an atomic snapshot across files. Save the game first when possible, or stop it for a consistent backup. Missing required save paths fail backup creation; missing optional paths are recorded in the archive.
Scheduled backups
Backup schedules offer Stop server during backup. When selected, Spark stops a running server, creates the backup, and attempts to start it again even if backup creation fails. A server that was already stopped remains stopped. The sequence runs as one operation on Spark and continues if the panel restarts. Follow its execution history and server status to confirm both the backup and restart completed. See Schedules to configure recurring work.
Restore a backup
Every restore asks for confirmation and explains which files will be replaced. If the server is running, the dialog offers to stop it, restore the backup, and restart it. Clear Restart server after restoring to leave it stopped instead. The panel waits for each operation to succeed before starting the next. Keep the page open until the sequence finishes. A failed restore never starts the server.
A full restore replaces all game files. A save-data restore replaces only the captured paths, including removing files added under those paths since the backup. Other installed files remain in place. Reinstall a compatible game version before restoring older save-data archives onto an empty server. Portable save-data backups install the game first when the destination is not installed. A server that was already stopped remains stopped after either restore type. Check its console after starting it or completing a restore with restart selected.
Each archive records its type and selected paths. Restoring an older backup uses that snapshot’s paths even if the Ember has changed.
Keep enough host space for the current game directory and a staged replacement
at the same time. Save-data restores also stage the installed files they preserve.
Restores assign files to the server’s runtime user and use private, writable
permissions: 0600 for files and 0700 for directories and executable files.
This prevents read-only permissions from blocking future saves.
Portable backups and recovery
When saved server values match the latest Ember, new backups also include the server settings and the complete Ember definition. Hidden variable values, including passwords and tokens, are included for exact recreation. Treat downloaded archives as sensitive credentials and store them privately. Import previews do not show hidden values.
To recover into an existing server, choose Upload backup in its Backups tab. After upload and validation, the archive appears in that server’s catalog. Stop the server, then choose Restore. Its current settings, ownership, and access grants remain in place. A full restore replaces its game filesystem; a save-data restore replaces only the paths captured in the archive.
To recreate a server, choose Create from backup in the Servers action menu and upload the archive. Review the recovered settings, select a destination Spark, and allocate new host ports. Ownership and access grants are configured on the destination; source placement and grants are not copied. A full backup restores the filesystem without running the installer. A save-data backup installs game files before restoring the captured paths. The new server remains stopped after restoration.
An administrator can import the included Ember if no matching definition exists. Its installer is executable code: only import backups from a trusted source. Other server creators can use backups whose Ember already exists in the panel. Recreating non-default hidden variable values requires an administrator, matching the existing restriction on changing hidden variables. Uploading requires backup creation permission; restoration requires the separate backup restore permission. Creating from backup also requires server creation access to the destination Spark.
Portable imports require embedded server settings and an Ember definition and can come from another Campfire installation. Data-only archives can be restored from their existing catalog but cannot be uploaded through this workflow. Review pending server-value changes before creating a portable snapshot. Backups made while that review is pending still protect data but omit portable server settings. Uploads use the configured file-upload limit and expire after one hour. Keep enough free space on the panel for the uploaded archive and on Spark for the archive plus staged restoration.
Name and pin snapshots
Use a backup’s actions menu to rename or pin it from the server’s Backups tab
or the main Backups page. These actions require server.backups.create.
Names are stored in the catalog; archive filenames and download/restore references
remain stable. Metadata can be edited while its Spark is disconnected.
Pinned backups keep their existing local and S3 copies regardless of age or count limits and do not consume the retention slots reserved for ordinary backups. When S3 synchronization is enabled, pinned local backups also sync regardless of their age. Unpin a snapshot to make normal retention rules apply again; an old snapshot may then be removed during the next cleanup. Unpinning is also required before manually deleting a backup. Deleting the server still deletes its backups, including pinned snapshots.
Off-host storage and retention
Configure the S3 bucket, region, optional compatible endpoint, and credentials
on the panel using the environment example.
For Docker, add these settings to the Compose service; merely adding variables
to .env does not forward settings absent from compose.yaml.
Enable backup synchronization separately on each server and configure its local and remote retention policies. Inspect synchronization errors before assuming an archive has an off-host copy. Failed synchronization retains the local archive. Configure local and S3 keep-last counts and maximum ages separately for Full server and Save data only backups. Frequent save-data snapshots do not displace retained full snapshots. Zero disables each individual limit. The panel and Sparks must be able to reach and trust the storage endpoint for upload and restore workflows.
Deleting a server also removes its local game data and backups. Keep a separate recovery copy when retiring a server. Game snapshots do not replace backups of the panel database and node identities; see installation backups and upgrades.