Skip to content
BENIBIX Learn

Recovery Point Objective (RPO)

Infrastructure💾 Backups & StorageDisaster Recovery

Also known as RPO

How much data you can afford to lose, measured in time.

Think of it like

It is like asking how much homework you could bear to lose. If you save each page, you lose none.

Example

Lucy's shop backs up once a night, so its RPO is 24 hours. Orders from the day could be lost. She moves to hourly backups to cut that to one hour.

Why it matters

It turns a vague wish into a number. That number decides how often you back up and what it costs.

Definition

The recovery point objective, or RPO, is how much data you can afford to lose, measured in time. An RPO of 24 hours means losing up to one day of changes is accepted. It is set by how often backups run. To get a smaller RPO, you back up more often or copy data all the time. It looks back from the moment of the disaster.
The RPO is the left span. It runs back from the disaster to the last good backup.

Common mistake

Mixing it up with RTO. RPO is how much data you lose. RTO is how long you are down.

Key takeaways

  1. 1
    Data loss. Measured in time.
  2. 2
    Looks back. From the disaster to the last copy.
  3. 3
    Set by schedule. More backups, smaller RPO.

Compare