lesson
30 min

Backups and Runbooks

Use the 3-2-1 backup rule, test your restores, and write runbooks so anyone can follow the steps.

What you will learn

By the end of this lesson, you can apply the 3-2-1 backup rule, check backup ages with code, and write a short runbook.

The 3-2-1 rule

A backup is a copy of your data you can use if the original is lost. The 3-2-1 rule is a widely used guide:

  • 3 copies of important data (the original plus two backups).
  • 2 different kinds of storage (for example, a cloud service and an external drive).
  • 1 copy kept off-site or offline, where an attacker or a fire cannot reach it.

A backup you never tested is a hope

Many organizations learn their backups do not work on the day they need them. Test a restore, which means actually getting files back from a backup, at least every few months. Pick a few files, restore them, and open them.

Check backup ages with code

Sysadmins often write small scripts to check things automatically. This one checks whether each backup is too old. The dates are fixed examples so the result is the same every time.

Run it. Which backups are too old? Then change max_age_days to 3 and run again.
Python 3
Ctrl+Enter to run | Tab to indent | Python runs in your browser via Pyodide

Runbooks: steps anyone can follow

A runbook is a short, step-by-step guide for a common task or problem. It lets someone other than the expert handle it, even under stress.

A good runbook has:

  • A clear title: "Restore a deleted file from the shared drive."
  • When to use it.
  • Numbered steps, one action each.
  • How to check it worked.
  • Who to call if it does not.

A national example

Backup plan check

0 of 5 done

Go deeper: Systems Administration, Simplified: A Practical Blueprint for Uptime, Security, and Scale

Ask. Answer. Build together.