Back up and restore a self-hosted server
Self-hosted servers back up their databases every 3 hours by default, and the owner can restore any snapshot from the Backups tab.
Your server backs up both databases every 3 hours and keeps snapshots for up to 12 months. The owner can restore any snapshot from Server Settings > Backups.
What a backup holds
Each backup is a timestamped folder in data/backups/, or in BACKUPS_DIR if you set it:
data/backups/2026-03-15_140000/
backup_community_2026-03-15_140000.db # channels, members, permissions, settings
backup_content_2026-03-15_140000.db # messages
manifest_2026-03-15_140000.json # list of uploaded files
files_backup_2026-03-15_140000.zip # uploaded files under 100 MB Files of 100 MB or more are stored once each in data/backups/large_files/ instead of in every snapshot. The activity log database (audit.db) is not backed up.
Snapshots are encrypted with the same key as the live databases, so only your server's binary can open them.
Retention
| Backup age | Kept |
|---|---|
| Up to 7 days | Every backup |
| 7 to 30 days | One per day |
| 1 to 6 months | One per week |
| 6 to 12 months | One per month |
| Over 12 months | Deleted |
Schedule
Under Backup Schedule in the Backups tab:
- Run automatic backups turns them on or off.
- Run every sets 1 to 168 hours. The default is 3.
- Include uploaded files in each backup adds the files zip. Off means databases and manifest only.
Click Save schedule. To back up right now, click Backup Now under Manual Actions. It works even with automatic backups off.
Restore a snapshot
Only the owner can restore.
- Open Server Settings > Backups.
- Find the snapshot under Files and Database Snapshots and click Restore.
- Click Restore & Restart to confirm.
The server saves a copy of the current databases, puts the snapshot in place and restarts. Members drop briefly and reconnect.
Anything changed after the snapshot, such as messages, channels and permissions, is lost. These stay as they are now: uploaded files, the activity log, LAN or VPN settings, the adult content setting and Website Widget settings.
Undo a restore
The copy made before the restore is in a pre_restore_<time> folder in your backups folder, as pre_restore_community_<time>.db and pre_restore_content_<time>.db. It is kept for 30 days and does not appear in the app. To go back to it, follow Restore by hand below with those two files.
Free up space
Reclaim disk space deletes the files zips from existing snapshots and clears large_files/. The database backups stay, so you can still restore any snapshot's databases.
To survive a disk failure, keep backups on another drive. See Store files or backups on another drive.
Restore by hand
Use this only when the server cannot start. Take both files from the same snapshot folder.
- Stop the server: stop the service or container, or close the server window.
- In your data folder, copy
community.db,content.dband any-waland-shmfiles next to them to a safe place. - Delete
community.db-wal,community.db-shm,content.db-walandcontent.db-shmfrom the data folder. - Copy
backup_community_<time>.dbinto the data folder and rename itcommunity.db. - Copy
backup_content_<time>.dbinto the data folder and rename itcontent.db. - On a Linux service install, run
sudo chown -R gamevox:gamevox <DATA_DIR>. - Start the server.
If it still fails, see Self-hosted server will not start.