Backup and recovery

Postgres is Tasuku's durable source of truth. A usable recovery set requires the database and its exact master key.

Back up

Include:

• all Tasuku Postgres databases and schemas;
• migration state;
• the exact active TASUKU_MASTER_KEY, TASUKU_MASTER_KEY_VERSION, and every configured TASUKU_PREVIOUS_MASTER_KEYS entry, stored separately from the database dump;
• deployment environment needed to reconstruct TASUKU_PUBLIC_URL, bootstrap policy, and worker access;
• custom agent runtime image definitions and remote-provider configuration.

Git repositories remain in GitHub, but Tasuku's review history, workflow events, credentials, repository settings, feedback, and learnings do not.

Restore

1. Stop the server and workers so no new leases or writes occur.
2. Restore Postgres.
3. Restore the matching active and previous master-key ring exactly.
4. Run migrations for the deployed Tasuku version.
5. Start the server and verify /healthz and /readyz.
6. Start one worker and inspect queue recovery before adding more workers.
7. Verify OAuth, GitHub App identity, repository synchronization, secret fingerprints, and one controlled workflow.

In-flight work

Queue leases are recoverable. After their lease expires, unfinished jobs can be reclaimed. Before manually replaying a command, inspect workflow events for external effects such as a GitHub comment, review, branch, or pull request that completed before the backup.