Define a recovery contract.
Write down the files, data, and checks required before calling a system recovered. Capture the baseline before backup selection so missing content cannot silently redefine success.

Hegarty Advanced Solutions / Learning
Learn the method. Run the lab. Check the result. Hands-on technical learning for people building and operating their own systems.
Recovery foundations
Prove your Docker backups actually restore.
A backup can be internally valid and still leave out something the application needs. RestoreLab turns that distinction into a practical exercise: capture a baseline, recover into a separate target, and inspect what came back.
The course uses a small PostgreSQL application and an encrypted restic repository. Run one complete recovery and one deliberately incomplete-backup drill. Learn why a successful backup command is only one part of the evidence.
What you’ll practise
Write down the files, data, and checks required before calling a system recovered. Capture the baseline before backup selection so missing content cannot silently redefine success.
Distinguish repository integrity, file checksums, database import, and application-data checks. Understand what each result establishes and what it leaves untested.
Take the disposable source offline and restore into a new target. Compare recovered records with the original baseline instead of relying on a database merely starting.
Use an incomplete backup to check that a missing required file is rejected. Identify the intended failure rather than treating every non-zero exit as a successful test.
The curriculum
Written explanations, practical exercises,
and a knowledge check in each lesson.
Replace a green backup indicator with explicit recovery requirements and an independently captured baseline.
Check the supported environment, start an isolated project, and inspect the original application data.
Understand the roles of a logical database dump, a required-file manifest, and the recorded backup snapshot.
Stop the disposable source, restore the selected snapshot, and import into a separate empty target.
Check required files and application contents, then interpret the report within the scope of the drill.
Run the negative control and explain why repository integrity can pass while recovery requirements fail.
Draft a recovery contract for an application you own and identify the additional work needed beyond this fixture.
Before you begin
Docker Desktop and remote Docker daemons are outside the tested support boundary. Comfort with a terminal and basic container concepts will help you follow the exercises.
The lab creates isolated projects with synthetic data, publishes no ports, and does not mount your existing applications. It stops its containers but retains volumes and local evidence for inspection.
Included in the product
This is a learning package, not a production recovery service. The same-host fixture does not establish off-site resilience or guarantee a recovery time for your own applications.
A self-directed completion record is not an accredited or identity-verified qualification. Product support covers the documented scope; see support terms for details.
Free to read / No purchase needed
Useful on their own,
or alongside a hands-on lab.
Planning
Define the workloads, choose a platform, and budget for storage, networking, and running costs before buying equipment.
Read the planning guideDeployment
Review persistence, network exposure, credentials, restart behaviour, and the update path before depending on an application.
Read the deployment guideRecovery
Inventory dependencies, keep independent copies, and practise a restore without overwriting the working system.
Read the recovery guideLooking for tools instead?
Meet Jarvis, the AI home assistant in development, and learn about future freeware releases.