Backups
Verification and recovery · backup record. On a deployment this row is a control; the demo shows the row with the reading its source supports.
Evidence
- Running
- 6 stores backed up; restore rehearsed 20 days ago
- Built
- 3 backups kept per store; older ones removed only after a newer verified backup exists
- Latest known
- every store within its cadence; rehearsal every 180 days
- Source
- deploy/aws/s3_store.tf
- Checked
- 2 hours ago
- Cadence
- every 180 days
- Mode
- record only
- State
- current
- Backup unit
- Each store, per its row: the updater's dumps under system/backups/, RDS automated backups, S3 versioning.
- Recovery
- Restore is one command the updater can run; a rehearsal is recorded per store on its cadence.
The five steps
Plan, back up, apply, verify, recover — in record only mode. On a deployment each step runs, is verified and lands on the audit trail; every component on the demo is current, so every step reads done.
- ✓ done Plan The last backup per store, where it is and its checksum are read from the journal and shown; there is nothing to confirm.
- ✓ done Back up The backups are the record; nothing further is copied here.
- ✓ done Apply Nothing is applied; a rehearsal restores one store to a scratch schema and records the date.
- ✓ done Verify Each store's last backup verifies against its checksum and its rehearsal is within 180 days.
- ✓ done Recover Nothing is recovered here; each component row names its own recovery step.
Every row behind this reading (6)
| Store | Where | Last backup | Checksum | Restore rehearsed | Retention |
|---|---|---|---|---|---|
| Records (object store) | S3 store bucket, versioning Enabled, KMS envelope (deploy/aws/s3_store.tf) | 2 hours ago | S3 version id and the recorded SHA-256 digest | 20 days ago | bucket versioning and lifecycle, per deploy/aws/s3_store.tf |
| Index (Postgres) | RDS automated backup; rebuildable from S3 by core.db.reconcile | 1 day ago | attested (RDS snapshot) | 20 days ago | var.db_backup_retention_days (default 1 day) |
| Operational state (platform_* tables) | store bucket, system/backups/ prefix, same KMS key | 5 days ago | SHA-256, verified by the updater | 20 days ago | 3 per store |
| config/ | beside the operational-state dump | 5 days ago | SHA-256, verified by the updater | 20 days ago | 3 per store |
| .env | never copied; presence and checksum recorded | 5 days ago | SHA-256 recorded, file never copied | 20 days ago | n/a: secrets stay where they are |
| Vocabulary schemas | the previous schema, kept on swap | 30 days ago | vocabulary counts, verified on swap | 20 days ago | one previous schema |
History
Applies and recoveries of this row, from the update journal. On a deployment every apply and every recovery lands here as it completes.
No apply or recovery recorded for this row. The demo's journal holds one completed update, of Running image.
Acknowledge: keep as is until <date> because <reason> — on a deployment this line is a form, audited as system.component_acknowledged; the demo shows the words.