Recovery Time Objective (RTO)

A recovery time objective (RTO) is the maximum time a system or business process can be down after an outage before the impact becomes unacceptable. It sets how fast recovery must happen and shapes backup and DR choices.

IntermediateCategory: Governance and compliance

Also called: RTO, maximum tolerable downtime, MTD

What is an RTO?

NIST defines the recovery time objective as the overall length of time a system's components can be in the recovery phase before negatively affecting the organization's business processes. Put simply: how long can you live without it?

An RTO is a target you set, based on business needs, not a measure of how fast you can actually recover. The gap between the two is what disaster recovery planning tries to close.

RTO vs RPO vs MTD

NIST's contingency planning guide, SP 800-34, uses three related measures, all set during a business impact analysis:

  • Maximum tolerable downtime (MTD): the total time a business process can be disrupted before the harm is unacceptable.
  • RTO: the time allowed to recover the systems that process depends on. It must fit within the MTD, with time left over to check data and resume work.
  • [Recovery point objective (RPO)](/glossary/recovery-point-objective/): how much data you can afford to lose, measured backward from the outage.

RTO is about time to recover. RPO is about data lost.

Examples

  • Online store checkout: RTO of 1 hour, since every hour down is lost sales.
  • Accounting system: RTO of 2 business days; payments can wait briefly.
  • Email: RTO of 4 hours.
  • Archive file share: RTO of 2 weeks.

What RTO means for your technology

Shorter RTOs cost more:

  • Days: restoring from cloud backups may be enough.
  • Hours: local backup appliances that can run servers directly from backup, or disaster recovery as a service.
  • Minutes: replication and automatic failover to a second site or cloud region.

Remember that a ransomware recovery takes longer than a simple restore, because systems must be investigated, cleaned and checked first. Test restores and time them against your RTOs. A managed IT or security provider can help set realistic targets.

Related terms

Sources

  1. Recovery Time Objective (glossary) (NIST)
  2. SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems (NIST)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.