As a leading solution provider in backup and disaster recovery, we have often engaged and discussed with customers about the RxOs. Just make it very clear for small and medium sized businesses, here is our quick take on it.
RPO – Recovery Point Objective:
RPO is the point in time to which systems and data must be recovered after an outage. It defines the amount of data loss that a business can endure.
An organization can plan for an appropriate BC technology solution on the basis of the RPO it sets. For Eg:
- If the RPO is 1 day, backups can be created at an offsite tape library daily at 00:00 Hours and the corresponding recovery strategy may be to restore data from the last set of backup tapes.
- If the RPO is 1 hour, database logs can be shipped to a remote site every hour and the corresponding recovery strategy may be to recover the database to the point of the last log shipment.
- If the RPO is less than 1 hour, data can be mirrored asynchronously to a remote site.
- If the RPO is zero, data can be mirrored synchronously to a remote site.
RTO – Recovery Time Objective:
RTO is the time within systems and applications must be recovered after an outage. It defines the amount of downtime that a business can endure and survive.
The RTO for a system helps determine appropriate recovery strategies. For Eg:
- If the RTO is 3 days, it may be appropriate to restore a system from tapes available at a cold site.
- If the RTO is 12 hours, a system can be restored from tapes available at a hot site.
- If the RTO is in order of a few hours, a system can be restored from disk-based backup, which gives faster restore than tape backups.
- If the RTO is a few seconds, it’s appropriate to use clustering production servers with bidirectional mirroring, enabling applications to run at two sites simultaneously.
It’s not just for you. It’s as important for us as well when it comes to RxOs. The plain reason is, we are because of you. We’re here to help!