Backup and restore1.x
Logical SQL dumps of databases, schedule/retention, upload/download/restore.
| Setting | What it does |
|---|---|
Enable daily backupbackup.schedule-enabled |
Writes a backup to /config/backups/ once a day. Default off. |
Daily run timebackup.schedule-time |
Minutes from midnight; uses TZ. Default midnight (0). |
Keep newest backupsbackup.retention-count |
Prunes older non-preserved backups; 0 = no pruning. Default 5. |
Each backup is a folder under /config/backups/ with db.sql (SQLite main database),
warden.sql and manifest.json. Download saves it as a ZIP; upload accepts a ZIP or
.sql file.
Actions: Create Backup, upload, and per backup Preserve, Download, Restore and Delete. Preserved backups are never pruned.
Migration database is disposable
Section titled “Migration database is disposable”Backups deliberately exclude usenet-migration.db (state for the experimental migration wizard under Settings → Migration). Deleting that file only loses migration bookkeeping, never mounted WebDAV content. If you restore a database backup mid-migration and the wizard shows many evicted releases, reset or forget migration data and re-scan; already-imported releases are re-detected and not resubmitted. See the migration guide.
Related
Section titled “Related”Restoring after SQLite Error 11 (“database disk image is malformed”)? See Database corruption.