1.3 KiB
1.3 KiB
Backup and restore
Current status
No production data or backup mechanism existed during the 2026-10-11 audit.
/var/backups/akyldash is a planned root-only location, not an active backup.
Do not report backup protection as enabled until an archive and restore have
both been checked.
Required release policy
- Create a backup before every production change, including any future schema or index migration.
- Include the normalized corpus,
search-users.sqlite3,search-reviews.sqlite3, the OpenSearch index/snapshot, deployment digest, and required secret file in the protected backup set. Store secrets separately with equivalent access controls. - Verify archive readability, checksums, and SQLite integrity before replacing the previous known-good backup.
- Keep one current pre-release backup. If deployment fails, retain the backup required to restore the previous state.
- Test restore into an isolated target before relying on the backup. Do not restore over production as a test.
The data is not yet managed by a tested backup script. Until that exists, the
owner must pause deployment and approve a maintenance window for a reviewed
backup/restore procedure. Copying live SQLite files with cp or an unchecked
tar archive is not an approved backup.