Backup, restore & integrity

Prove a backup can be restored

Lesson 15 of 20 · 12 min · Module 5: Evidence and tested recovery

A recovery copy is useful only if it can restore the data you need.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • Make the recovery copy before the risky change
  • Restore into a verifiable state

The idea

This practice runbook is an ordered sequence of the teaching actions named in the task. Each action changes or observes the supplied in-memory scenario.

steps:
  - action: backup
    name: practice-copy
  - action: restore
    name: practice-copy
  - action: verify

01Make the recovery copy before the risky change

A backup made after corruption faithfully preserves the wrong state. Timing is part of the recovery contract.

02Restore into a verifiable state

A restore command completing is not enough. Read back the restored data and compare it with an expected content or integrity check.

03Keep independent copies in real systems

This in-memory exercise demonstrates ordering and integrity. Real backups need separate failure boundaries, protected access, retention, and repeated restore tests.

Your turn

The initial data is {notes:["first note"]}. In the practice runbook: backup named before-change, corrupt the live data, restore before-change, then verify. End with the original data and a passing verification.

What the checks look for

  • Keeps the original recovery copy
  • Restores the expected data
  • Tests the failure between backup and restore
Try it in the editor →

Take this with you

Test recovery outcomes, not merely backup-job completion.

Go a little further

Describe an off-host restore test and how you would verify its result.

Learn Infrastructure & Operations for free

20 short lessons with real code and instant checks.

See the whole course →