Recovery Point Objective (RPO): Difference between revisions

From BCMpedia. A Wiki Glossary for Business Continuity Management (BCM) and Disaster Recovery (DR).
Jump to navigation Jump to search
No edit summary
 
(No difference)

Latest revision as of 14:01, 24 July 2024

1. Recovery Point Objective or RPO is the point in time to which systems and data must be recovered after a disaster has occurred.
BL-B-5 Click to know more

For example, data should be restored up till the start of the day. It includes the amount of data needed to be re-constructed after the systems or functions have been recovered.

Simply explained, RPO:

  • is how much data a business can lose during a disaster.
  • helps organisations prioritise their backup and recovery strategies.
  • is a snapshot of the organisation's data at a specific point in time.
  • define the point in time when an organisation has to restore its data after a disruption.


Related Terms: Recovery Objectives, Objective, Recovery Time Objective (RTO), Minimum Business Continuity Objective


BCM Institute's Professional Training and Certification
BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1B: Foundation (BC)


BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1C: Foundation (CM)


BCMBoK Competency Level
BCMBoK 3: Business Impact Analysis CL 1D: Foundation (DR)




{{#ev:youtube|43E6-2NUHiQ|400}}

Click to know more about expert level training

(Source: Business Continuity Management Institute - BCM Institute)

Recovery Objectives: RTO, RPO and MTPD
Recovery Objectives: RTO, RPO and MTPD

2. Point in which information used by an activity must be restored to enable activity to operate on resumption.

A Manager’s Guide to ISO 22301 Standard for Business Continuity Management System

Note : Can also be referred to as "maximum data loss".

(Source: ISO 22301:2012 – Societal Security – Business Continuity Management Systems - Requirements) - clause 3.44

3. The point in time to which systems and data must be recovered after a disruption has occurred. For example, data should be restored up till start of the day.

(Source: Singapore Standard 540 - SS 540:2008)

4. The point in time to which work should be restored following a Business Continuity E / I / C that interrupts/disrupts the business e.g. ‘start of day’.

(Source: Business Continuity Institute - BCI)

5. The point in time to which systems and data must be recovered after an outage. (e.g. end of previous day's processing). RPOs are often used as the basis for the development of backup strategies, and as a determinant of the amount of data that may need to be recreated after the systems or functions have been recovered.

(Source: Disaster Recovery Institute International / Disaster Recovery Journal - DRII/DRJ)

(Source: Australia. A Practitioner's Guide to Business Continuity Management HB292 - 2006 )

6. The point in time to which systems and data must be recovered after an outage (e.g. end of previous day's processing). RPOs are often used as the basis for the development of backup strategies and as a determinant of the amount of data that may need to be recreated after the systems or functions have been recovered.

(Source: Malaysia BCM Standard MS1970:2007)

7. The capability at a pre-disruption point in time to which systems and data must be recovered after an outage (e.g. to end of previous day’s processing).

(Source: AS/NZS 5050.2 Australian and New Zealand Standards for business continuity management.

Part 2: Business continuity management practice standard)