Backup and recovery
What to back up
Section titled “What to back up”At minimum preserve:
config.yml;- the master key file when file-backed;
- the SQLite database as a consistent snapshot;
- optional artwork, AniBridge mappings, exports, and source-observation caches.
The database contains provider instances, encrypted credentials, profiles, features, baselines, mappings, ignores, list bindings, run history, and audit state.
SQLite WAL backup
Section titled “SQLite WAL backup”Brokerr uses WAL mode. The safest simple backup is to stop the container, copy
the data directory, then restart it. For an online backup, use a SQLite-aware
backup command rather than copying only app.db while writes are active.
Never delete app.db-wal or app.db-shm while Brokerr is running. Their absence
while the database is idle is normal after a checkpoint; WAL mode is confirmed
with PRAGMA journal_mode, not by permanent sidecar files.
Restore
Section titled “Restore”Restore the database and the exact matching master key. Start Brokerr and check Diagnostics before running a sync. If the key does not match, encrypted provider credentials cannot be decrypted and targets must be reconnected.
Configuration export
Section titled “Configuration export”Brokerr does not currently provide a portable export of provider instances, credentials, profiles, feature state, and managed-list bindings. The runtime configuration export covers application settings only. Run JSON/CSV exports are audit artifacts, not a database or profile backup, and cannot reconstruct credentials or feature state.