Ad · 728×90 desktop · 320×50 mobile

The RTO/RPO conversation with the business

Published 2026-04-24 · Disaster Recovery

Business stakeholders have opinions about tolerance for downtime and data loss. Those opinions are usually "zero." Your job is to get to realistic numbers.

The wishful phase

Left to their own devices, business stakeholders will answer:

  • Downtime tolerance: 0 minutes
  • Data loss tolerance: 0 seconds

That's not actionable. It's also usually not what they actually want once they understand the cost.

The pricing phase

Show them this table:

RTORPOStrategyRelative annual cost
24+ hrs24 hrsBackup & Restore1x baseline
4 hrs1 hrPilot Light2x baseline
15 min5 minWarm Standby4x baseline
< 1 min< 1 minActive/Active8x baseline

Now the conversation changes. "You're saying it would cost 4x to go from 4-hour to 15-minute RTO? Let's talk about which systems really need that."

The per-system conversation

Not every system has the same RTO/RPO. A customer-facing payment system has dramatically different needs than an HR vacation tracker. Build a table:

SystemBusiness impactRTO targetRPO targetStrategy tier
PaymentsRevenue loss + PR5 min1 minWarm standby
Customer portalCX impact30 min5 minPilot light
Internal ticketingProductivity24 hr24 hrBackup & Restore
Analytics DWDelayed reports72 hr24 hrBackup & Restore

The test commitment

Once RTO/RPO are set, commit to testing quarterly. Without tests, the numbers are fiction.

Tools

Ad · 300×250 responsive

Joined by engineers at enterprises running the systems you build. No spam. No tracking in the emails.