Restore Rehearsal Card

Local recovery evidence

Know your backup
comes back.

Restore into an isolated Compose target. Check health and row counts. Leave with a signed Markdown card instead of a hopeful checklist.

Run your first drill Read the source
  • Typed commands
  • No telemetry
  • Ed25519 signed
A backup capsule passes through an isolated glass basin and two verification beacons before reaching a signed evidence card.
01 Backup02 Isolate03 Assert04 Sign

Not “backup completed.”

“Service healthy. 18,402 rows. RTO met. Signature valid.”

One declared path

From artifact to evidence.

Every operation is explicit, timed, and contained. A failure creates evidence too.

  1. 01

    Fingerprint the input

    Record SHA-256 and byte count without opening backup contents in the report.

  2. 02

    Build a clean boundary

    Refuse host networking, bind mounts, external volumes, privileged services, and production-like targets.

  3. 03

    Ask useful questions

    Check container health, exact row-count ranges, and declared exit codes—not just process completion.

  4. 04

    Sign what happened

    Write a portable Markdown card with timings, checks, RTO outcome, and an embedded Ed25519 signature.

A small binary, no agent

Your weekly drill in three commands.

Requires Docker Compose. The CLI itself never phones home.

restore-rehearsal.toml
$ cargo install --git https://github.com/B-Divyesh/sf-restore-rehearsal-card
$ rrc init
$ rrc run --confirm-target restore-card-weekly --output weekly.md

Recorded demo

A passing run, line by line.

No Docker needed to preview the operator flow.

$ rrc run --confirm-target restore-card-weekly
✓ backup.dump  84.2 MB  sha256:7f9a…c31d
✓ isolated target started  4.18 s
✓ restore command exited 0  output omitted
✓ database healthy  1.04 s
✓ accounts: 18,402 rows  expected ≥ 1
PASS · 41.22 s / 300 s RTO · card signed

Failure is a result

Break the restore now.
Not during the incident.

A bad checksum, failed command, unhealthy service, missed count, or breached RTO produces a signed failed card and exit code 4 for CI. Cleanup still runs.

Optional team layer

The CLI stays free.
The meeting gets sharper.

The Operator Pack adds reusable review material for teams that need a consistent recovery ritual. It never gates cards, verification, export, accessibility, or safety.

$39 USD

One-time purchase · updates included

  • Weekly rehearsal runbook
  • Failure review agenda
  • RTO decision log template
  • Six service profile worksheets
Get the Operator Pack
Have a license? Restore purchase

Stored only in this browser. Paste the complete token from your receipt.

Checkout and refunds are handled by Sociobot/Dodo, the merchant of record. Terms · Privacy

The useful artifact

A backup is a promise.
A rehearsal is evidence.

Start with the free CLI