How long can the system be unavailable?
How much data can we afford to lose?
The first answer helps define your Recovery Time Objective: how quickly service must return.
The second helps define your Recovery Point Objective: how far back your recoverable data may be.
“Immediately” and “nothing” are popular answers until the cost of achieving them arrives.
Recovery requirements must be based on business impact, not optimism.
<img src="https://media.daily.dev/image/upload/s--e-YaRd9m--/f_auto/v1787033653/ugc/content_d0e432d7-0803-4cfc-8eba-ac10e800745f?_a=BAMAMicg0" alt="aws21.png">
#AWSWithoutTheFluff #DisasterRecovery #BusinessContinuity

Smiley Face

Ezile Mdodana

Two key business questions - acceptable downtime and acceptable data loss - form the basis for Recovery Time Objective (RTO) and Recovery Point Objective (RPO). These recovery requirements should be driven by actual business impact rather than aspirational answers like 'immediately' and 'nothing', since achieving near-zero RTO/RPO comes with real cost tradeoffs.

Day 21/30: Two questions every business should answer

A recovery plan should put a price beside every RTO and RPO option before the business picks one