# Recovery Time Objective (RTO)

> The longest time a system may be down after it breaks.

**Field:** Infrastructure  
**Category:** Backups & Storage  
**Also known as:** RTO

## Think of it like

It is like a shop that must open again two hours after a pipe bursts. The clock starts when the water does.

## Definition

The recovery time objective, or RTO, is the longest time a system may be down after a failure. An RTO of 4 hours means service must be back within 4 hours. It decides how fast the restore must be, and whether you need a spare system ready. It looks forward from the moment of the disaster.

## Example

A hospital sets a 1-hour RTO for patient records. Restoring from tape would take 6 hours, so it keeps a ready copy in a second data centre.

## Why it matters

It decides how much you spend on being ready. A short RTO needs spare systems, and they cost money every day.

## Common mistake

Setting an RTO without timing a real restore. If the restore takes 8 hours, a 2-hour target is only a wish.

## Three principles

- **Downtime.** The longest allowed break.
- **Looks forward.** From the disaster to service back.
- **Drives cost.** Shorter means more spares ready.

## Related terms

- [Recovery Point Objective (RPO)](https://learn.benibix.com/term/infrastructure/recovery-point-objective)
- [Disaster Recovery](https://learn.benibix.com/term/infrastructure/disaster-recovery)
- [Data Restore](https://learn.benibix.com/term/infrastructure/data-restore)
- [Mean Time to Recovery (MTTR)](https://learn.benibix.com/term/infrastructure/mean-time-to-recovery)
- [High Availability (HA)](https://learn.benibix.com/term/infrastructure/high-availability)

## Told apart from

- [RPO vs RTO](https://learn.benibix.com/compare/recovery-point-objective-vs-recovery-time-objective): People mix up RPO and RTO, and they measure two things. RPO is how much data you can afford to lose. It looks back from the disaster to the last good backup. RTO is how long you can afford to be down. It looks forward from the disaster until service is back. Backing up more often shrinks the RPO. A faster restore shrinks the RTO.

![A timeline. On the left, the last good backup. In the middle, the disaster. On the right, the moment service is back. The span from the last backup to the disaster is marked RPO, the data you lose. The span from the disaster to service back is marked RTO, the time you are down. The restore sits inside the RTO span.](https://learn.benibix.com/diagrams/inf2-rpo-rto.svg)

---

Source: https://learn.benibix.com/term/infrastructure/recovery-time-objective
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
