Prove one archive restore through observable consistency checks
A backup report says Success without reading restored documents. Add a repeatable restore exercise and recorded checks.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Verification · Operations
Estimated field mix
- Quality engineering40%
- Storage systems30%
- Site reliability30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional archive Alder backs up synthetic document metadata and generated blobs into a dedicated local directory. No real organizational data or cloud accounts are required.
Setup prerequisites
- Create synthetic metadata and generated blob fixtures.
- Provide isolated source backup and restore directories.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CBACK-101 · Define archive backup manifests with explicit format versions
- CBACK-102 · Exclude temporary archive uploads from backup inventories
- CBACK-103 · Verify archive backup bytes against manifest digests
- CBACK-104 · Capture archive metadata and blob references at one snapshot boundary
- CBACK-105 · Resume archive backup copying without accepting stale partial files
- CBACK-106 · Finalize archive backups with an explicit complete marker
- CBACK-107 · Refuse archive restore paths outside the selected target directory
- CBACK-108 · Restore archive backups into an isolated staging generation
- CBACK-109 · Switch restored archive authority with a rollback pointer
Acceptance criteria
- Restored references resolve
- Document counts match manifest scope
- Excluded temporary data stays excluded
Implementation constraints
- Report local fixture results and unresolved assumptions.
Verification to include
- Read every small fixture object
- Remove one restored blob and detect failure
Deliverables
- Restore exercise and result record
Rollout and recovery
Reclassify the backup as unverified if checks fail.
Value of the work
For the engineer: Practice consistent snapshots and recoverable restoration.
For the team: Inspect whether backup success can be substantiated by a usable restore.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.