A Recorded Restore Check

One reproducible local restore, with the measured result and its limits.

What ran

At 2026-09-12 08:50:46 UTC, the eval harness generated a blog-shaped SQLite database, replicated it through Borela's embedded Litestream agent into a file replica, and restored it into a fresh path while the agent was still running. A second isolated restore ran through the same verification path as borela-agent verify.

The restored file passed SQLite integrity_check. The first restore also matched the source database's schema, per-table row counts, and SHA-256 content hashes. This is a real local execution against generated data, not a customer database or a production R2 drill.

go test ./internal/eval -run '^TestEmbeddedRestoreCorrectness/blog$' -count=1 -v

Recorded result

The numbers below are the observed result of that run, not a guarantee for future runs. Duration depends on machine and replica size.

checked_at: 2026-09-12T08:50:46Z
integrity_check: ok
application tables: 3
rows: 3021
restored bytes: 921600
restore duration: 15 ms
source schema, row counts, content hashes: match

What it does not prove

This run does not exercise production R2 credentials, email delivery, or a live customer's backup history. Those require a separately recorded production drill before making a production reliability claim.