Glossary
RTO
Definition
Recovery time objective is the target time for restoring a system or service after a disruption.
RTO stands for recovery time objective. It describes the downtime target for a service, not how much data you can lose.
A customer may include “RTO” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
RTO stands for recovery time objective. It is the time a business aims to take to restore a disrupted system or service. The target connects a technical recovery plan to a practical question: how long can this part of the business remain unavailable?
For example, a small distributor might set a four-hour RTO for order processing because staff can handle a short backlog manually. Its historical marketing archive may have a longer target. These are hypothetical choices; the right times depend on commitments to customers, alternative ways of working and the effect of delay.
An RTO is a planning objective, not evidence of actual recovery speed. Retrieving a backup, rebuilding a server, restoring permissions and checking the application all take time. A provider's support response time may only measure when someone starts investigating, rather than when the service works again.
Agree what starts the clock and what counts as restored. Include the dependencies needed for staff to perform the task, then record the result of a realistic recovery exercise. RTO differs from RPO, which describes the point in time to which data should be recovered. A service can return quickly with unacceptably old data.