Glossary

RPO

Recovery point objective

Definition

Recovery point objective is the target for how far back in time recovered data may be after a disruption.

RPO stands for recovery point objective. It sets how recent the recovered data needs to be, usually expressed as a period of time.

A customer may include “RPO” 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.

RPO stands for recovery point objective. It describes the point in time to which data should be recovered following a disruption. Businesses often express it as a maximum period of recent changes they are prepared to lose.

Suppose an online retailer chooses a one-hour RPO for orders. If its database fails at noon, the recovery design should support a usable copy from 11am or later. Recovering yesterday's database would miss that target, even if the restoration itself took only minutes. The retailer would also need a way to reconcile orders recorded elsewhere.

Backing up every hour does not automatically prove a one-hour RPO. A job can fail, a copy can be corrupt, or the latest copy may already contain the damage. Monitoring and recovery exercises help establish how recent a usable recovery point actually is.

Set the maximum data loss the business can tolerate for each service, then compare that target with backup intervals and transaction capture. Measure recovery points in tests; RPO does not describe restoration time or how long copies are kept. Distinguish RPO from retention, which concerns how long copies remain available, and RTO, which concerns the time needed to restore service. Each answers a different recovery question.

Sources

NIST: recovery point objective