Make a backup job succeed while restoring nothing

short · 45 min · Objective 3.2

Task

Reproduce the failure the lesson describes: a job that reports success and produces nothing usable. Cause it three different ways, so you recognise the shape rather than one instance of it.

Steps

  1. Set up a backup job over lab/data/ that reports success and writes an archive. Confirm a normal restore works, so you have a baseline.
  2. Fault one -- WRONG SCOPE: add a new directory to the dataset that the job's selection does not include. Run the job, confirm it reports success, restore, and record what is missing in lab/false-success.md.
  3. Fault two -- INCONSISTENT CAPTURE: start a writer continuously modifying a file, back up without quiescing, restore, and record whether the restored file is coherent.
  4. Fault three -- UNREADABLE DESTINATION: make the backup target unwritable partway through, or truncate the archive afterwards. Record what the job reported versus what the restore produced.
  5. For each fault, write the check that would have CAUGHT it, and note which of the three a tag-based selection would prevent.

Verify

grep -Eci 'scope' lab/false-success.md
grep -Eci 'consisten|quiesc' lab/false-success.md
grep -Eci 'truncat|unreadable|corrupt' lab/false-success.md
grep -Eci 'tag' lab/false-success.md

All four non-zero. Each fault must record both what the job said and what the restore produced -- the gap between those two is the entire lesson.

This is an independent study companion for CompTIA Cloud+ CV0-004 and is not produced by or endorsed by CompTIA.