What is the difference between RTO, RPO, and MTPD?
Direct answer
RTO (Recovery Time Objective) defines how quickly a process must be restored after a disruption. RPO (Recovery Point Objective) defines how much data loss is acceptable, measured in time. MTPD (Maximum Tolerable Period of Disruption) defines the absolute maximum time a process can be unavailable before the impact becomes unacceptable to the organisation.
How do RTO, RPO and MTPD fit together?
The three values answer different questions about the same disruption:
- MTPD is the outer limit. It is set by the business: how long can this process stay down before the damage to customers, finances, legal obligations or reputation becomes unacceptable?
- RTO is the target for getting the process back. It must sit within the MTPD, with enough margin to absorb a recovery that goes less well than planned.
- RPO looks backwards from the moment of failure. It says how much data, measured in time, you can afford to lose and re-create. An RPO of four hours means backups or replication must never leave more than four hours of data at risk.
RTO and MTPD are about time to recover; RPO is about data. A process can have a long RTO and a very short RPO, for example a ledger that can wait a day to come back but cannot lose a single transaction.
Where do these objectives come from?
They are outputs of a business impact analysis. For each process you describe what happens as an outage lengthens, find the point where the impact becomes unacceptable (the MTPD), and set the RTO and RPO inside it. ISO 22301, the international standard for business continuity management systems, places this work in its business impact analysis and risk assessment (clause 8.2).
Regulation now asks for the same reasoning:
- DORA (Regulation (EU) 2022/2554) requires financial entities to develop and document backup, restoration and recovery procedures (Article 12). In determining the recovery time and recovery point objectives for each function, they must take into account whether it is a critical or important function and the potential overall impact on market efficiency (Article 12(6)).
- NIS2 (Directive (EU) 2022/2555) lists business continuity, such as backup management and disaster recovery, and crisis management among the cybersecurity risk-management measures of Article 21(2)(c).
See who DORA applies to and NIS2 scope.
What mistakes make recovery objectives unreliable?
- Setting the RTO longer than the MTPD, or equal to it, so any delay in recovery breaches the limit.
- Choosing values IT can deliver instead of values the business needs, then never comparing the two.
- Using free-text values per team (“ASAP”, “half a day”, “4h”), which cannot be compared or aggregated.
- Setting objectives for processes but not for the assets and suppliers they depend on, so a system or provider with a slower recovery quietly sets the real RTO.
- Never testing them. DORA Article 11(6) requires ICT business continuity and response and recovery plans to be tested at least once a year.
A shared list of time thresholds, the same for every process and asset, removes the third problem and makes the others visible.
How are RTO, RPO and MTPD kept in Acuna GRC?
In Acuna GRC, RTO, RPO and MTPD are fields on each process and on each asset, chosen from the Time Threshold list your administrator maintains. The BIA Overview in the Operate workspace lists every process in BIA scope with its impact assessment, its RTO and its earliest impact, so a process whose RTO comes after its first serious impact stands out. Impact scenarios record what happens as an outage lengthens, each with a severity and a time threshold, and the SPOF analysis lists assets that support several critical processes.
How Acuna GRC handles it
In Acuna GRC, all three are set per process and per asset from a Time Threshold list your administrator maintains, so values are comparable across processes and assets, and the BIA Overview shows each process's RTO beside its earliest impact.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
- Solution
DORA
Keep one ICT third-party register, map critical processes with RTO and RPO, find single points of failure and follow ICT incidents in one place.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 11 and 12
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(c)
- ISO 22301:2019, Business continuity management systems, clause 8.2
This page explains the rules in general terms and is not legal advice.
Frequently asked
Can the RTO be longer than the MTPD?
No. The MTPD is the point at which the impact becomes unacceptable, so a recovery target beyond it plans for an unacceptable outcome. Set the RTO within the MTPD, with a margin.
Is RPO the same as backup frequency?
No. RPO is the business requirement: how much data, in time, you can lose. Backup or replication frequency is how you meet it, and it must be at least as frequent as the RPO requires.
Who should set the MTPD?
The business owner of the process, because it reflects business impact. IT and continuity teams then check whether the RTO and RPO inside it can actually be achieved.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

