Recovery Point Objective (RPO)

A recovery point objective (RPO) is the maximum amount of data, measured in time, that a business can afford to lose in an outage. An RPO of four hours means backups or replication must capture data at least every four hours.

IntermediateCategory: Governance and compliance

Also called: RPO, acceptable data loss

What is an RPO?

NIST defines the recovery point objective as the point in time to which data must be recovered after an outage. Put simply: how much recent work can you afford to lose?

If you back up every night at midnight and a server fails at 5 p.m., you lose 17 hours of data. If your RPO is 24 hours, that's acceptable. If it's 1 hour, it's not, and you need more frequent backups or replication.

RPO vs RTO

  • RPO looks backward from the outage: how much data is lost.
  • [RTO](/glossary/recovery-time-objective/) looks forward from the outage: how long until the system is back.

A system can have a short RPO and a long RTO, or the reverse. Payroll data might need an RPO of minutes (no lost transactions) but tolerate an RTO of a day.

Examples

  • Point-of-sale or ordering system: RPO of minutes; lost orders mean lost revenue and angry customers.
  • Accounting database: RPO of 1 hour.
  • Shared documents: RPO of 4 to 24 hours.
  • Archived records: RPO of a week.

What RPO means for your backups

Your backup frequency has to be at least as frequent as your RPO:

  • 24 hours: nightly backups.
  • 1 to 4 hours: frequent snapshots or incremental backups.
  • Minutes or zero: continuous replication or database log shipping.

Ransomware considerations

With ransomware, your most recent backup may already contain encrypted files, or attackers may have been inside for weeks. Keep multiple restore points going back far enough to find a clean copy, and protect them with immutable or offline storage. Cloud sync services aren't backups: they can copy encrypted files over good ones.

A managed IT or security provider can design backups to meet your RPOs and test them.

Related terms

Sources

  1. Recovery Point Objective (glossary) (NIST)
  2. SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems (NIST)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.