TIPS AND INSIGHTS
RTO vs RPO: what your recovery commitments really mean
RTO and RPO are commitments, not aspirations. But most organisations state them without proving they can meet them. Here is what they really mean — and how to make them defensible.
RTO: how fast can you recover?
Recovery Time Objective (RTO) is the maximum acceptable time between a disruption and the resumption of a critical process. It is a commitment to your customers, your regulators, and your board. If you say your RTO is 4 hours, you are promising that the process will be back within 4 hours.
The problem is that most RTOs are stated, not tested. An organisation claims a 4-hour RTO, but has never actually tested whether it can recover in 4 hours. When disruption hits, the gap between the commitment and reality becomes painfully clear — and expensive.
RPO: how much data can you lose?
Recovery Point Objective (RPO) is the maximum acceptable data loss measured in time. If your RPO is 1 hour, you can lose at most 1 hour of data. This determines your backup frequency and your replication strategy. An RPO of 0 means no data loss — which is expensive and often unnecessary.
RPO is about data, RTO is about process. They are related but different. A process might have a 4-hour RTO (we will resume within 4 hours) and a 1-hour RPO (we will lose at most 1 hour of data). Both need to be tested, not just stated.
Making commitments defensible
A defensible RTO is one you have tested. You ran the recovery exercise, measured the actual time, and confirmed it meets the commitment. If the test took 6 hours and your RTO is 4, you have a gap — and the gap is now visible before the crisis, not during it.
This is the difference between a promise and a proof. Regulators and boards increasingly demand proof. “We have a 4-hour RTO” is a promise. “We tested our recovery and achieved 3.5 hours” is proof. One survives scrutiny. The other does not.
Explore Business Continuity (BCM)
See how this module works in practice and what it can do for your organisation.