Backup and recovery

Local guidance available; production design planned

The current environment is a development foundation. It records which state is authoritative, but it does not yet provide a supported production backup, restore, retention, or disaster-recovery procedure.

Current expectations

• Back up PostgreSQL with PostgreSQL-native dump and restore tools.
• Treat Redis as replaceable cache and queue state under current development assumptions.
• Rebuild Meilisearch from PostgreSQL through Scout import and index synchronization.
• Preserve repository, artifact, and configuration state once those planned services become authoritative.
• Keep secrets outside source control and back them up through the installation’s approved secret-management process.

Local preservation

docker compose down stops the environment and preserves named volumes.

docker compose down --volumes is destructive. It removes Compose-managed databases, indexes, messages, and installed dependency volumes.

Production gate

Before a production deployment is supported, Katra must publish and prove:

• PostgreSQL backup and point-in-time recovery expectations
• Repository and artifact backup
• Configuration and secret recovery
• Upgrade compatibility and rollback
• Meilisearch rebuild
• Redis durability assumptions
• Recovery objectives and a reproduced restoration exercise

For help planning a current evaluation environment, see Support.