RPO & RTO

Write measurable recovery objectives

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

Recovery planning needs both a data-loss objective and a time-to-recover objective.

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…

  • Distinguish the two objectives
  • Connect objectives to a procedure

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.

01Distinguish the two objectives

RPO describes an acceptable recovery point, commonly expressed as how much recent data can be lost. RTO describes the target time to restore useful service.

02Connect objectives to a procedure

A stated objective needs an actual backup frequency, restore process, available capacity, and verification. Writing a number does not achieve the target.

03Measure a real drill separately

The practice steps verify ordering and content. A real recovery drill should record elapsed time and the age of the recovered data against the objectives.

Your turn

Add recovery_objectives with rpo_minutes 15 and rto_minutes 30. Then backup daily, corrupt, restore daily, and verify. These are declared objectives; the model does not claim to measure real recovery time.

What the checks look for

  • Declares both objectives correctly
  • Completes a verified restore
Try it in the editor →

Take this with you

State recovery targets, then measure real drills against them.

Go a little further

Explain what backup schedule could support a fifteen-minute RPO.

Learn Infrastructure & Operations for free

20 short lessons with real code and instant checks.

See the whole course →