Backup and Recovery
Back up Clouisle metadata, indexes, queues, and upload assets
A recoverable Clouisle backup includes at least PostgreSQL, Qdrant, upload storage, and deployment configuration/Secrets. Redis mainly holds queues, caches, and session state; whether to back it up depends on the organization's recovery requirements for unfinished tasks.
What to Back Up
| Content | Role | Recommendation |
|---|---|---|
| PostgreSQL | Users, teams, resources, configuration, audit, document metadata | Daily full backup + continuous archiving |
| Qdrant | Document vectors | Coordinate with database backups |
| Upload storage | Raw documents, attachments, media, and sandbox artifacts | Keep at the same point in time as PostgreSQL metadata |
.env/Kubernetes Secret | Connection and signing configuration | Store encrypted; never commit to the repository |
| Redis | Celery/cache/session | Decide according to task recovery requirements |
Recovery Order
- Restore PostgreSQL and dependent extensions.
- Restore Qdrant collections and uploaded files.
- Restore Secrets and environment variables; confirm
SECRET_KEYstays consistent. - Start the API; confirm health and database migrations.
- Start Worker, Sandbox Worker, and the single Beat.
- Check document status, vector dimensions, Agents, Workflows, and API Keys.
- Run one Knowledge Base retrieval and one Agent/Workflow smoke request.
Restoring only PostgreSQL leaves resources missing raw files or vectors; restoring only Qdrant leaves vectors that cannot be linked. Metadata, files, and indexes must be handled at the same recovery point.
How is this guide?