Back to glossary
R
Definition

RTO IT definition

Recovery Time Objective: the maximum acceptable length of time a service can be down after an incident before the business impact becomes critical. It is the target time to restore service after a disaster.

The RTO (Recovery Time Objective) is the maximum acceptable time between a disruption and the return to an operational service. It answers a simple question: "how long can we go without this service before the impact becomes unbearable?"

Together with the RPO, the RTO is one of the two metrics that underpin any Disaster Recovery Plan (DRP) and that are committed to in SLAs.

How to set an RTO

The RTO is determined application by application during the Business Impact Analysis (BIA) of the BCP. The more critical a service, the shorter its RTO:

  • Minutes: e-commerce site, payment system, real-time messaging.
  • Hours: ERP, CRM, back-office business applications.
  • Days: secondary internal tools, non-urgent reporting.

RTO and cost

The RTO is the main cost driver of a DRP: targeting a 5-minute RTO (automated failover, active-active infrastructure) costs several times more than a multi-hour RTO (restore from backup). The goal is to align the RTO with actual criticality, without over-investing in non-essential services.

RTO vs RPO

The RTO measures a recovery time; the RPO measures an acceptable data loss. A service may tolerate a long outage (high RTO) while accepting no data loss (near-zero RPO), or the other way around.

Frequently asked questions

What is the difference between RTO and RPO?

+

The RTO (Recovery Time Objective) is the maximum time to restore a service after an outage. The RPO (Recovery Point Objective) is the maximum amount of data you can afford to lose, expressed as a time span. RTO is measured in downtime duration, RPO in data lost since the last usable backup.

How do I define the right RTO?

+

The RTO is set during the Business Impact Analysis (BIA), application by application, based on how critical the service is. A revenue-generating real-time service requires an RTO of a few minutes, while a secondary internal tool may tolerate several days. The RTO directly drives the cost of the recovery architecture.

Need help mapping your IT landscape?

Kabeen helps you inventory, analyze and optimize your application portfolio.

Try for free