Difference between revisions of "Recovery Point Objective"

From Open Risk Manual
(Initial Entry)
 
 
Line 1: Line 1:
 
== Definition ==
 
== Definition ==
'''Recovery Point Objective '''. The point in time to which data is restored and/or systems are recovered after an outage. have been recovered. RPO for applications can be enumerated in business time (i.e., business hours after a Sunday disaster restores to close of business Thursday) or elapsed time, but is always measured in terms of time before a disaster. RPO for systems typically must be established at time of disaster as a specific point in time (e.g., end of previous day’s processing) or software version/release. The point to which information used by an In purely IT DR terms it activity must be restored to enable the can be seen as the precise activity to operate on resumption. time to which data and transactions have to be restored (e.g. close of business, last intra-day backup). Can also be referred to as maximum data loss
+
'''Recovery Point Objective '''. (RPO) The point in time to which data is restored and/or systems are recovered after an outage.  
 +
 
 +
* RPO for applications can be enumerated in business time (i.e., business hours after a Sunday disaster restores to close of business Thursday) or elapsed time, but is always measured in terms of time before a disaster.  
 +
* RPO for systems typically must be established at time of disaster as a specific point in time (e.g., end of previous day’s processing) or software version/release.  
  
 
[[Category:Business Recovery Strategy]]
 
[[Category:Business Recovery Strategy]]

Latest revision as of 13:22, 30 April 2021

Definition

Recovery Point Objective . (RPO) The point in time to which data is restored and/or systems are recovered after an outage.

  • RPO for applications can be enumerated in business time (i.e., business hours after a Sunday disaster restores to close of business Thursday) or elapsed time, but is always measured in terms of time before a disaster.
  • RPO for systems typically must be established at time of disaster as a specific point in time (e.g., end of previous day’s processing) or software version/release.