DevOps Foundations · Module 7: Operations, observability and backup · Lab
Back Up Fixture Data and Restore It to a Wiped Target
50 min hands-on · Core
Small fixture dataset plus a backup tool (restic or platform equivalent); source and wiped restore target both under /tmp/dlab-m07-02.
Two ways to do this lab: in your browser on Killercoda (free, no install), or on your own machine as a local guide. Killercoda runs one free scenario at a time: if you see a waiting queue, close other Killercoda tabs and wait a minute.
Objectives
- Back up fixtures with recorded schema and context
- Restore to a separate wiped target, never over the original
- Verify with checksums and time the restore against an RTO
Step 1
Back up with context
Back up the fixtures recording schema version, app version that reads the format, and backup time. State an RPO and an RTO in numbers before restoring.
Step 2
Restore to a wiped target
Wipe the separate target directory, restore the backup there, replay any recorded migration step, and start the fixture app against the restored data.
Step 3
Verify and time it
Compare checksums between source and restored data, run the fixture read path, and record wall-clock restore time against the stated RTO with a pass or fail verdict.
How to confirm it worked
- Backup recorded with schema version and stated RPO/RTO
- Restore performed on a separate wiped target with migration replayed
- Checksums match between source and restored data, quoted
- Timed result compared to the RTO with a verdict and drill report