CBACK-103 · Describe backup content

Verify archive backup bytes against manifest digests

Practice briefTaskIntermediate

Copy completion alone marks backup success. Stream verification of every required object before success.

Focused work estimate: 2h + prerequisites
Priority in the scenario: High
Engineering practice: Hashing · Streaming

Estimated field mix

Storage systems100%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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.

Use in my work board View project and downloads

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.

Acceptance criteria

Digest and size both match
Missing object fails verification
Failure identifies logical object safely

Implementation constraints

Do not buffer entire backups in memory.

Verification to include

Verify generated fixture
Flip one copied byte

Deliverables

Streaming verifier and corruption cases

Rollout and recovery

Mark affected backups unusable until reverified.

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.