Recovery Point Objective (RPO)

The Recovery Point Objective defines the maximum acceptable data loss, measured in time: how far back the last usable copy may be. It exists because data protection has a price that rises steeply as the RPO approaches zero. The management decision behind it is how much to invest in replication and backups versus how much lost work the business can re-enter or absorb. For data-heavy services in Gulf financial centres this is a board-visible number, not an IT detail.

The process owner and IT propose the RPO from the value of the transactions at stake, management approves it, and it is recorded in the BIA and in the technical DR specifications. A trading platform may need an RPO of 5 minutes, which dictates continuous replication; an HR system may live with 24 hours and a nightly backup. The link is mechanical: the RPO directly sets the required backup or replication frequency. RPO also pairs with RTO — one says how fresh the data will be, the other how fast the service returns.

A common failure is declaring RPO zero everywhere without funding the replication that zero implies, leaving a target no infrastructure can meet. Another is never restore-testing backups, so the real RPO stays unknown until the worst day. The economics of these choices are worked through in ERGP module M3, Impact analysis and the economics of recovery.