Finalize archive backups with an explicit complete marker
Operators select directories still being copied. Publish a durable completion marker only after required verification.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Atomic publication · Durability
Estimated field mix
- Storage systems80%
- Site reliability20%
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
Acceptance criteria
- Incomplete directories are not selectable
- Marker binds manifest digest
- Failure cannot leave valid-looking completion
Implementation constraints
- Marker creation follows verification acknowledgement.
Verification to include
- Finish valid backup
- Crash before marker creation
Deliverables
- Finalization protocol and tests
Rollout and recovery
Withdraw completion marker if later validation fails.
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.