Homelab Academy / Modules
Orient, prior check, guided practice, required Feynman, reflect.
Module: Segmentation, Backup & Power
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Distinguish disaster recovery from backup creation, high availability, and routine incident response.
Bloom level: Understand / Apply
Last reviewed: 2025-03-08
Distinguish disaster recovery from backup creation, high availability, and routine incident response.
Practice a controlled disaster-recovery exercise that validates backup integrity, measures recovery time, confirms restored data, records evidence, and improves a recovery runbook without affecting workloads outside the classroom directory.
Complete the module reading first:
Explain disaster recovery to a new homelab operator using a notebook backup as the analogy. Your explanation must distinguish owning a copy from proving that the copy can restore useful work.
A backup is like a photocopy of a notebook. Disaster recovery is the full plan for finding the right photocopy, obtaining a replacement notebook, copying the information back, checking that no pages are missing, and deciding that people may use it again. RPO says how much writing we are willing to lose because it happened after the photocopy. RTO says how long we are willing to wait before the notebook is usable. A drill measures what actually happens and reveals missing supplies or unclear instructions before a real emergency.
Can I explain why a successful backup job does not prove recoverability?
Can I state the difference between an objective and an observed result?
Can I describe at least one case where matching file hashes would still be insufficient?
Can I identify the failure domains this laboratory does not test?
Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.