Backups
RAG-DocBot ships an opinionated backup/restore runbook and a single entry-point script that backs up Postgres, Qdrant, and branding assets in one shot.
tip
Always prefer ./backup.sh over running pg_dump / Qdrant snapshot calls by hand. The script handles compose service discovery, Qdrant collection enumeration, manifest generation, and archive packaging consistently.
What gets backed up
backup.sh covers all stateful components managed by the deployment:
| Component | Source | Output inside backups/<timestamp>/ |
|---|---|---|
| PostgreSQL | pg_dump against the compose postgres service | postgres.sql.gz |
| Qdrant | Snapshot API for every discovered collection | qdrant/<collection>--<snapshot>.snapshot |
| Branding assets | ./branding/ directory | branding.tar.gz |
| Run metadata | Component versions + git SHA | MANIFEST.txt |
Local GGUF model files under models/ are intentionally not included — they are large, immutable, and should be managed out-of-band (e.g. mirrored from your model registry or object store).
Running a backup
From the repository root of your RAG-DocBot deployment:
./backup.sh