System Recovery Time Objective

From BCMpedia. A Wiki Glossary for Business Continuity Management (BCM) and Disaster Recovery (DR).
Revision as of 14:45, 9 January 2023 by Moh heng (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
BL-B-5 Click to know more
1. System Recovery Time Objective (RTO) refers to the period within which systems and applications must be recovered after a disruption has occurred to carry out the recovery of business functions.


Notes (1): The RTO is comprised of the following components: Starting from the point of disaster, the time before a disaster is declared, the time to perform tasks (as documented in the BC or DR plan) to the point of business resumption whereby the data which was lost, up to the point of disaster, is restored. See the complete diagram of these three concepts shown below.

Notes (2): System Recovery Time Objective (RTO) refers to the maximum acceptable length of time that can elapse before an IT application is returned. It should not exceed the RTO of the Business Function attached.

  • How long does the IT team or vendor "promise" to bring your system up once it is disrupted? Is it stated in their service level agreement (SLA)?
  • Within what period of time must the system be recovered after the disruption?

Related Terms: Recovery Objectives, Recovery Point Objective (RPO), Recovery Time Objective (RTO)

BCM Institute's Professional Training and Certification
BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1B: Foundation (BC)


BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1C: Foundation (CM)


BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1D: Foundation (DR)



Click to know more about expert level training
Recovery Objectives: RTO, RPO and MTPD
Recovery Objectives: RTO, RPO and MTPD

(Source: Business Continuity Management Institute - BCM Institute)