Services

Resources

Company

RTO and RPO

RTO and RPO are the two main targets in disaster recovery. Recovery time objective (RTO) is the longest a service may stay down after a failure before the business impact is unacceptable. Recovery point objective (RPO) is the most data, measured in time, the business can afford to lose. Both are set per system or user journey.

How it works

RPO is driven by how often data is copied. With backups every hour and no replication, a failure can lose up to 60 minutes of writes, so the RPO is at best 1 hour. Continuous replication can bring RPO down to seconds. RTO is driven by how fast you can detect the failure, decide to fail over, restore data and shift traffic. A team with a 30-minute RTO needs restores and cutover runbooks that finish well inside that window.

Why it matters in production

Tighter RTO and RPO cost more, through standby capacity, replication and drills. Setting them per user journey keeps spend focused. Untested targets are guesses. Only regular restore and failover drills show whether you can meet them.

See also

On the One2N blog

References

  1. Disaster recovery options in the cloud (AWS whitepaper)

  2. Recovery time objective (NIST glossary)

Comic about RTO and RPO: a shop's order database crashes at 9:50; the last backup was 9:00 and service returns at 10:15, so 50 minutes of data is lost (RPO) and it is down 25 minutes (RTO); the business limits are 1 hour of loss and 30 minutes down, so both are within limits; tighter limits cost more, and the team practises restoring to prove they meet them.