Backup and Restore
Backup and Restore
Document backup and restoration capabilities once verified.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Protected data, procedures, prerequisites, restore validation and known recovery limitations. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
The sibling backup tool implements SQL-export and referenced-R2 verification plus B2 upload/readback and a manifest published last. Its documentation records an unresolved FTS/export blocker and no completed cloud restore. This audit did not query providers or verify current provider export support.
Use its source audit, export options, manifest contract and isolated restore acceptance procedure. Local synthetic/mocked test claims are distinct from an actual retained production backup.
Corpus archives and public certificates do not include all private retry/schema/operational state. Restore requires fencing, independent identity configuration and fresh lineage; follow Corpus recovery. Do not infer recovery readiness from archive maxima or successful content responses.
