Skip to content
BENIBIX Learn

RPO vs RTO

People mix up RPO and RTO, and they measure two things. RPO is how much data you can afford to lose. It looks back from the disaster to the last good backup. RTO is how long you can afford to be down. It looks forward from the disaster until service is back. Backing up more often shrinks the RPO. A faster restore shrinks the RTO.

Infrastructure💾 Backups & Storage

Recovery Point Objective (RPO)

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

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.

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.
Full entry
Infrastructure💾 Backups & Storage

Recovery Time Objective (RTO)

The longest time a system may be down after it breaks.

The recovery time objective, or RTO, is the longest time a system may be down after a failure. An RTO of 4 hours means service must be back within 4 hours. It decides how fast the restore must be, and whether you need a spare system ready. It looks forward from the moment of the disaster.

Example
A hospital sets a 1-hour RTO for patient records. Restoring from tape would take 6 hours, so it keeps a ready copy in a second data centre.
Why it matters
It decides how much you spend on being ready. A short RTO needs spare systems, and they cost money every day.
Full entry

In one line

Recovery Point Objective (RPO)
How much data you can afford to lose, measured in time.
Recovery Time Objective (RTO)
The longest time a system may be down after it breaks.