Back Up and Restore¶
Backups are admin-managed full SQLite database snapshots. They can contain sensitive information for every user, so protect them like the live database.
This page explains how admins create, list, restore, and schedule backups of the server-wide database, where they are stored, and what to do before restoring.
What can an admin do with backups?¶
The Admin panel can:
- Create a backup immediately
- List backup history
- Download a selected backup
- Restore a selected backup
- Delete a selected backup
- Import a backup file
- Run the configured scheduled-backup job immediately
Restore creates a pre-restore backup before replacing the database.
How do I schedule a recurring backup?¶
Scheduled backups are disabled by default. An admin can select:
| Setting | Default |
|---|---|
| Enabled | false |
| Frequency | daily |
| Time | 02:00 |
| Retained scheduled backups | 2 |
Weekly schedules run on Sunday at the configured time.
Where are backups stored?¶
Docker defaults to /data/backups. Keep /data persistent and ensure only
trusted operators can read or copy that volume.
Warning
Backup and export encryption is not implemented. Use filesystem permissions, encrypted storage, and protected transfer channels.
Next steps¶
- Get a full server reference for backup operations in the Operations Runbook.
- Move user-owned data without touching the server in Move Data In and Out.
- Configure persistent storage paths in Database Paths.