Recovery Time Objective (RTO)
Definition
The maximum acceptable duration of downtime before a system must be restored to service. RTO drives decisions about recovery method: a short RTO may require hot standby or replication, while a longer RTO allows restoration from backup media.
- Measures
- Maximum acceptable downtime
- Unit
- Time
- Drives
- Choice of recovery method
- Short RTO example
- Hot standby or replication
Common questions
Why would a short RTO require hot standby rather than restoring from backup media?+
Restoring a system from backup media involves retrieval, verification, and rebuild time that can exceed a tight downtime tolerance, so organisations with a short RTO instead run a live or near-live standby system that can take over with minimal switchover delay.
Does a longer RTO mean an organisation cares less about the incident?+
Not necessarily. A longer RTO often reflects a realistic assessment of how a lower-priority system's downtime actually affects operations, letting the organisation invest recovery budget where a short RTO delivers more business value.
Related terms
- Clean Baseline
- A confirmed, verified system state that predates the compromise and is free from attacker artefacts. Establishing a clean baseline is the starting...
- Dependency Mapping
- The process of identifying all services, systems, and data flows that a given system depends on, and all systems that depend on...
- Observation Window
- A defined period after a system is restored during which enhanced monitoring is applied before the system is declared fully recovered. The...
- Recovery Point Objective (RPO)
- The maximum acceptable amount of data loss measured in time. It defines how far back in time the organisation is willing to...
- Rollback Plan
- A documented procedure for reverting a recovery attempt if it fails or introduces new problems. A rollback plan specifies trigger conditions, the...