In disaster recovery, what does the Recovery Point Objective (RPO) describe?
How much data loss is tolerable, measured back to the last good backup.
- The point in time to which data must be recoverable ✔
- The time needed to rebuild a server
- The distance to the backup site
Why: RPO looks backward in time: if backups run nightly, you might lose up to a day of data. A lower RPO needs more frequent backups or replication. It is not part of the maximum tolerable downtime.
Huh, didn't know that: NIST says backup frequency should be based on how critical the data is and how often new information arrives.
My RPO is one sandwich. If you eat my lunch, I can only recover up to the last bite.
References
Answer: The point in time to which data must be recoverable. RPO looks backward in time: if backups run nightly, you might lose up to a day of data. A lower RPO needs more frequent backups or replication. It is not part of the maximum tolerable downtime.
- NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf
The RPO represents the point in time, prior to a disruption or system outage, to which mission/business process data can be recovered
Checked 2026-10-10. - NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf
Unlike RTO, RPO is not considered as part of MTD.
Checked 2026-10-10. - NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf
based on data criticality and the frequency that new information is introduced
Checked 2026-10-10.
Think this answer is wrong? Tap "Challenge this answer" on the card in the game and tell us why.
More stuff everyone should know
That's stuff everyone should know.