Skip to main content
Legia

IT Infrastructure & Cloud

What are RPO and RTO?

Also called RPO, RTO, recovery point objective, recovery time objective.

Short definition

RPO (recovery point objective) is the limit on how much data may be lost in a disaster, measured backward from the time of the incident. RTO (recovery time objective) is the limit on how long a system may be down until it is running again.

How to read them

An RPO of 24 hours means the company accepts losing at most one day of data, so daily backups are enough. An RPO of 15 minutes means backups or replication must run at least every 15 minutes. An RTO of 4 hours means the system must be usable again no later than four hours after the disruption. Both are business decisions that are then translated into technical choices.

Example in a company

A point-of-sale app used across many branches might need an RPO of a few minutes and an RTO of one to two hours, because every hour of downtime means sales on hold. An internal document archive might be fine with an RPO of one day and an RTO of two days. Setting the same target for every system is usually too expensive for non-critical systems, or too loose for critical ones.

From targets to reality

The smaller the RPO and RTO, the higher the cost: continuous data replication, standby servers that are always ready, and frequently rehearsed procedures. Targets only mean something if they are tested. Measure the actual recovery time during drills, then compare it with the agreed RTO. If it falls short, fix the process or adjust the target together with management.

Related Legia service Server Installation & Management Setup, hardening, monitoring, and migration for physical, virtual, and cloud servers.