A reference diagram distinguishing Recovery Point Objective (data loss tolerance) from Recovery Time Objective (downtime tolerance) on a shared disaster-recovery timeline.
RPO measures how much data you can afford to lose, looking backward from the disaster to your last good backup. RTO measures how long you can afford to be down, looking forward from the disaster to full restoration.
Last reviewed 2026-09-30
What this shows
Recovery Point Objective and Recovery Time Objective plotted on the same incident timeline, showing why they answer two different business questions — how much data you can afford to lose, versus how long you can afford to be down.
Intended audience
IT leaders, business continuity planners, and auditors scoping or reviewing a disaster-recovery plan.
Methodology
Built from the standard disaster-recovery-planning definitions of RPO and RTO (the incident-to-restoration timeline model used across NIST SP 800-34 and general DR planning practice) — not a proprietary framework, and not specific to any one backup product or vendor.
Limitations
Illustrates the concepts and their relationship, not a specific organization’s actual recovery capability. Real RPO/RTO figures depend on backup frequency, infrastructure, and tested recovery procedures — this diagram does not substitute for a real recovery test.
Citing this resource
To reference this resource, link directly to this page — e.g. “IT KORR’s RPO vs. RTO: Two Different Clocks, itkorr.com/technical-resources/rpo-vs-rto.” This page may be linked to and quoted from with attribution; republishing or redistributing the diagram itself requires separate permission.
