4.1 RTO & RPO (Doshi) Flashcards
Recovery Point Objective (RPO)
A recovery point objective (RPO) is the period for which recent data will be irretrievably lost in a disaster.
Extend of acceptable data loss:
It’s called Recovery Point Objective or RPO.
RPO POINT is most concerned by data loss
RPO measures:
RPO is usually measured in hours or days.
Recovery Time Objective:
Recovery time objective (RTO) is the period from the onset of an outage until the resumption of service.
Extend of acceptable system downtime?
It’s called Recovery Time Objective or RTO
RTO Time is for system downtime.
RTO measures:
RTO is usually measured in hours or days.
What does a RTO of 2 hours indicate?
that organization needs to ensure that their system downtime should not exceed 2 hours.
What does a RPO of 2 hours indicate?
that organization needs to ensure that their data loss should not exceed 2 hours of data captured.
What should a RTO for a critical system be?
Zero or near Zero
What should a RPO for a critical data be?
Zero or near Zero
The lower RTO or RPO:
The higher the cost of maintenance environment
What does a low RTO or RPO indicate?
That disaster tolerance is low. Therefore, if disaster tolerance is low, RTO/RPO should be low.
What is recommended when RTO is low?
A mirrored site or hot site
What is recommended when RPO is low?
Mirror imaging or real time replication for data back-up is recommended
What is recommended when RPO is zero?
Synchronous data backup strategy to be used
The lower the time requirements for RTO & RPO:
The higher, the cost of recovery strategies.
RTO of 2 hours indicates that organization needs to ensure that their system downtime
should not exceed 2 hours.
RPO of 2 hours indicates that organization needs to ensure that their data loss should
not exceed 2 hours of data captured.
In any given scenario, for critical systems, RTO is
zero or near zero. Similarly, for critical data, RPO is zero or near zero.
In any given scenario, lower the RTO/RPO,
higher the cost of maintenance of environment.
In any given scenario, low RTO/RPO indicates that
disaster tolerance is low. Other way round, if disaster tolerance is low, RTO/RPO should be low.
In any given scenario, when RTO is low,
mirrored site or hot site is recommended.
In any given scenario, when RPO is low,
mirror imaging or real time replication for data back-up is recommended.
In any given scenario, where RPO is zero,
synchronous data backup strategy to be used.
Both RTO & RPO are based on
time parameters. The lower the time requirements, the higher the cost of recovery strategies.
