Coming soon. This course is planned; lessons and labs are not available yet. No release date has been announced.
Plan a recovery point, back up service state, restore into a clean target and verify that clients receive the right data.
Intermediate ยท Service backup and recovery
Know Linux files, permissions, services and a basic client request path. This plan builds on service operation rather than fleet configuration rollout.
The planned project asks you to restore a Linux service from a stated failure, account for the recovery point and prove useful client behavior.
One disposable Linux service and its data, from backup design through a verified clean restore.
3 planned chapters and 6 lesson outlines.
Decide which state and dependencies must survive, and how much data loss the recovery point permits.
Planned task: Map data, configuration, credentials, ownership and dependencies before designing a backup.
Changed case to investigate: A second host stores one dependency elsewhere; find it before claiming the inventory is complete.
Planned task: Relate a backup method to live writes and state the latest recoverable transaction.
Changed case to investigate: A file copy races an in-flight write; identify the data gap and choose a safer capture point.
Create a bounded backup and prove that its contents can be used on a clean target.
Planned task: Back up the agreed state, check archive integrity and inspect whether each required item is present.
Changed case to investigate: A credential is intentionally excluded from the archive; identify the separate recovery dependency.
Planned task: Recover data and configuration with the right ownership, access and credential path.
Changed case to investigate: The target uses a different service UID; correct ownership without broadening access.
A running process is not enough: compare data and client behavior with the contract.
Planned task: Check representative restored records and a client read/write path, then record remaining data loss.
Changed case to investigate: The process answers but serves stale data; locate the missed recovery point.
Planned task: Repeat the restore when the original host is unavailable and hand off the evidence and limits.
Changed case to investigate: The backup destination is reachable but one dependency is not; justify the next safe step.