Warm-standby: measured RTO/RPO from a tested ser8 restore #264

New issue

Closed

opened 2026-06-07 05:27:15 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-07 05:27:15 +00:00

Owner

Warm-standby follow-up from #99. Run a tested restore end to end and capture the measured RTO and RPO — not estimates. Restore the latest shipped snapshot onto ser8, time the promote, confirm workloads come back, and record the numbers (and the gaps found) back into the machine-kai-ser8 skill / #99.

This is the proof the DR story is real. Depends on snapshot-ship + promote runbook.

Warm-standby follow-up from #99. Run a **tested restore** end to end and capture the **measured** RTO and RPO — not estimates. Restore the latest shipped snapshot onto ser8, time the promote, confirm workloads come back, and record the numbers (and the gaps found) back into the `machine-kai-ser8` skill / #99. This is the proof the DR story is real. Depends on snapshot-ship + promote runbook.

coilysiren added the

label

2026-06-17 07:05:52 +00:00

coilysiren commented

2026-06-17 08:22:33 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:22:34 +00:00