What Is a Recovery Point Objective (RPO)?
A recovery point objective (RPO) is the most data a client can afford to lose, measured as time back from the moment something fails. An RPO of four hours means you need a restorable point at least every four hours, because everything since the last good point is gone.
RPO and RTO Answer Different Questions
RPO asks how much work the client loses. Recovery time objective (RTO) asks how long until they're working again. Different things set them. RPO comes from how often you capture and how quickly a copy reaches somewhere safe. RTO comes from how you recover: booting a server from its image is a different answer from downloading it. Pulling two terabytes down a 100 Mbit line takes about 44 hours at full speed, before anything boots. A client can have a tight RPO and a slow RTO, so agree both.
Side by Side
| Compared on | RPO | RTO |
|---|---|---|
| The question it answers | How much work is lost? | How long until they're working? |
| Measured as | Time back to the last good point | Time from failure to running again |
| Set by | How often you capture, and how fast copies reach safe storage | How you recover, your bandwidth and your hardware |
| Broken by | A backup that stopped, or a copy that never arrived | A restore that has to download everything first |
How to Set an RPO for a Client
Start with what an hour of lost work costs the client, one system at a time. Staff might recreate a morning's edits on a file server. A finance database that changes all day is another matter. Write the RPO per system into the DR plan, then set the backup schedule to beat it. And don't promise a number you can't measure. An RPO only means something if you can show the age of the last restorable point at any moment.
How EnterProtect Measures It
EnterProtect judges health against when the next recovery point was due, not the last job's exit code, so a resource outside its objective shows as an RPO breach as soon as it slips. Microsoft 365 runs on a four-hour cycle on every tenant. File Backup schedules run hourly, every four hours, daily or on a custom schedule. In BCDR, a required off-site copy that falls behind its objective makes the resource unhealthy even while the local point is fine. And every DR test records measured RPO and RTO against the plan's targets.
RPO Questions MSPs Ask
Is RPO the same as backup frequency?
Not quite. Frequency is how often a backup starts. RPO is about the newest point you could actually restore right now. A backup that runs hourly but hasn't finished, hasn't reached off-site storage or can't be restored doesn't meet a one-hour RPO.
What's the difference between RPO and retention?
RPO is how recent your newest restorable point is. Retention is how far back the oldest one goes. Most clients need both: a short RPO for this morning's mistake and long retention for the auditor who asks about last year.
What RPO should a small business have?
Set it per system, not per business. Ask what an hour of lost work costs on each one, then schedule backups to beat that. Continuous capture multiplies storage and infrastructure for an RPO a small-business server rarely justifies.
Can You Show Your RPO Right Now?
EnterProtect BCDR flags a server as soon as it slips outside its objective and records measured RPO and RTO in every DR test.
More Answers
See Every AnswerWhat Is the Difference Between File Backup and Image Backup?
A file backup copies the files, folders and databases you choose.
How Should an MSP Price Backup for Clients?
Charge per protected unit (a mailbox, a server, a workstation) at or under a published list price your client can check.
How Often Should Microsoft 365 Be Backed Up?
Several times a day, because the gap between captures is the most work a client can lose.