Recovery time objective (RTO) and recovery point objective (RPO)
Concept
RTO defines how fast a system must be back online after a failure, and RPO defines how much data loss is acceptable; both are business requirements that drive resilient design.
Description
Recovery time objective (RTO) and recovery point objective (RPO) are the two central recovery targets in business continuity and disaster recovery planning. The recovery time objective is the longest period an application may be unavailable after an incident. The recovery point objective is the longest period of data loss that is acceptable during an incident. In short, RTO answers the question of how fast a system must be back online, and RPO answers the question of how much data the business can afford to lose. Both are business requirements rather than purely technical settings, and they drive how resilient solutions are designed.
The Azure Well-Architected Framework page on defining reliability targets places RTO and RPO within a wider set of reliability targets. These fall into availability, correctness and recovery categories, and the recovery category is where RTO and RPO sit. The same page names MTTR and MTBF alongside them. Together, the recovery targets express how effective business continuity and disaster recovery plans and tests are. The page does not give universal numeric values; the right figures depend on the workload and on what the business can tolerate.
According to that guidance, RTO and RPO values are derived from failure mode analysis together with continuity and disaster recovery plans and tests. They are not chosen in isolation. For each component, teams should define thresholds that trigger recovery, and those thresholds should allow for transient faults so that recovery does not start too early. Platform guarantees also have to be considered: Microsoft publishes RTO and RPO guarantees only for certain products, so a design cannot assume that every service comes with such a commitment.
Targets have to be agreed with stakeholders, because the acceptable downtime and data loss are business decisions. They are also not fixed for all time. The guidance notes that they can change as workload complexity, customer count or technology changes, which means they should be reviewed rather than set once. The page also warns that workloads not properly tested against recovery metrics should not carry guaranteed SLAs. A target that has never been exercised in a recovery test is an assumption, not a verified capability.
In practice, RTO and RPO influence concrete design choices such as how often data is backed up or replicated, whether recovery happens within one region or across regions, and how much redundancy is built in. A short RPO generally calls for more frequent protection of data, while a short RTO calls for recovery processes that can bring a system back quickly. These trade-offs are the reason the targets are set early: they frame what backup, restore and replication strategies need to achieve.
The M365.FM episode "Harden Azure Backup with Soft Delete, MUA, and Vault Lock" (2025-12-07) touches on this in the context of governing Azure backups. The episode lists defining recovery objectives as a key component of a governance framework: establish the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) so that they align with business resiliency and compliance needs. It places this alongside designing redundancy, with backup, restore and replication strategies across cloud and on-premises environments and consideration of regional and cross-regional recovery, and alongside implementing protection mechanisms. In that framing, RTO and RPO act as the starting point against which the rest of the backup design is measured.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is the difference between RTO and RPO? (AI)
The recovery time objective (RTO) is the longest period an application may be unavailable after an incident. The recovery point objective (RPO) is the longest period of data loss that is acceptable during an incident.
How are RTO and RPO values determined? (AI)
According to the Azure Well-Architected Framework guidance, they are derived from failure mode analysis together with continuity and disaster recovery plans and tests, and agreed with stakeholders. The page gives no universal numeric values.
Does Microsoft guarantee RTO and RPO for all services? (AI)
No. The guidance states that Microsoft publishes RTO and RPO guarantees only for certain products, so platform guarantees have to be checked per service when defining targets.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: