Course contentsShow
← System Design
Lesson 1420 of 1,91935. Backup and Disaster RecoveryFree lesson

Business Impact Analysis for RPO/RTO

Determining appropriate RPO/RTO targets by analyzing business impact, revenue loss, and compliance requirements per service.

Business Impact Analysis for RPO/RTO

What you'll learn: How to determine the right RPO and RTO targets for each service by quantifying business impact, revenue exposure, and compliance constraints.

The Core Idea

Not all services are equal. Your user-facing payment API losing 10 minutes of transaction data is catastrophic—losing 10 minutes of analytics logs is barely noticeable. Business Impact Analysis (BIA) is the structured process of identifying what each service's downtime and data loss actually cost your organization, so you can set appropriate RPO/RTO targets and justify the investment needed to meet them.

Analyzing Business Impact

Start by asking three key questions for each service:

1. Revenue Impact

How much money is lost per hour of downtime? For an e-commerce checkout service, calculate: average transactions per hour × average order value. A service generating $50,000/hour justifies aggressive RTO targets (minutes, not hours) and expensive hot-standby infrastructure.

2. Compliance and Legal Requirements

Financial services might face regulatory fines for data loss beyond strict thresholds. Healthcare systems must meet HIPAA requirements. These aren't negotiable—your RPO is dictated externally, regardless of cost.

3. Reputation and Customer Trust

Some impacts are harder to quantify but equally critical. A social media platform's messaging service going down for hours damages user trust permanently, even if direct revenue loss is low.

Setting Targets from Analysis

Rank services into tiers:

  • Tier 1 (Critical): RPO < 5 minutes, RTO < 15 minutes → synchronous replication, multi-region active-active
  • Tier 2 (Important): RPO < 1 hour, RTO < 4 hours → asynchronous replication, hot standby
  • Tier 3 (Standard): RPO < 24 hours, RTO < 24 hours → daily backups, cold standby

This analysis transforms RPO/RTO from abstract numbers into budget-backed engineering requirements.

Key Takeaway: Business Impact Analysis quantifies downtime costs and compliance risks per service, enabling data-driven RPO/RTO targets that balance availability needs against infrastructure investment.