I85PREP
⌘ K
CCRTS study materials
CCRTS study resources

CCRTS: Business Impact Analysis and Recovery Objectives (RTO/RPO)

CCRTS · Work through your exam, one topic at a time.

All guide sections

Business Impact Analysis and Recovery Objectives (RTO/RPO)

From business impact to recoverability

The exam tests whether you can derive RTO and RPO from business impact rather than from infrastructure convenience. A BIA identifies critical business functions, the impact of disruption over time, dependencies, and the maximum tolerable downtime (MTD or MTPD). RTO is the target time to restore the function after disruption; it must be shorter than MTD to leave time for validation and business resumption. RPO is the maximum acceptable data loss measured in time; it drives backup frequency, log shipping, and replication mode. Work recovery time is the time needed to validate data and resume normal processing.

Core rules

  • Impact categories include financial, regulatory, contractual, reputational, safety, and operational. Impact usually rises steeply after a threshold, which helps set MTD.
  • Map each business function to applications, data, infrastructure, people, facilities, and third parties. RTOs cascade downward: an application supporting a four-hour function cannot itself have a six-hour RTO unless a manual workaround exists.
  • Tier functions and systems. Tier 1 may need continuous availability and near-zero RPO; Tier 3 may tolerate days. Document assumptions and dependencies, including identity, DNS, and network.
  • RPO is not the backup schedule. A nightly backup gives an RPO of up to 24 hours; five-minute RPO needs continuous replication or frequent log backups, plus verification.
  • Validate objectives with business owners, then test them. Update the BIA after mergers, cloud migrations, or process change. ISO 22301 frames BIA within a business continuity management system.

Worked example

A payment processor has an MTPD of eight hours. Business owners set RTO at four hours and RPO at five minutes. The team chooses synchronous replication within a region and asynchronous replication to a second region with a five-minute lag, plus transaction-log backups every five minutes. Because the RTO includes validation, the runbook reserves one hour for reconciliation. If the second region can only restore in six hours, the design fails the RTO and needs a warm standby or manual fallback.

Traps

Do not set RTO equal to MTD; that leaves no validation time. Do not confuse RPO with retention. Do not write objectives without business sign-off or funding. Do not ignore dependent systems and vendors-an application cannot recover faster than its identity or data tier. Do not leave the BIA static.