LOCAL TEST REPORT
A recovery result you can inspect.
A disposable Docker fixture was deliberately corrupted, then restored into fresh volumes from an exact encrypted snapshot. The original source was not overwritten.
7 October 2026 · 16:46 CESTRestic 0.19.1Fixture · 11.22 s
Before and after SHA-256 match
BEFORE
47c2a80899add036b931a061dee15d22ddff66f06f8502516be23932db6b4bc3
AFTER
47c2a80899add036b931a061dee15d22ddff66f06f8502516be23932db6b4bc3
- Encrypted Restic snapshot and restore --verify
- Equal app fixture hashes
- Original corrupted fixture remains untouched
- Full Restic repository data check
Open the original JSON evidence →Test boundaries
- Fixture run on Docker Desktop, macOS arm64; not a production RTO or SLA.
- This test does not validate public HTTPS, offsite retrieval, externally delivered alerts or a complete restored Kuma login.
- Kuma outage/recovery and wrong-password rejection remain pending after the shared engine failure. Linux and actual version-change rollback are not verified.
Source is included in the archive. Review and repeat a restore drill for your own application before production.
