Application RTO and RPO Explained – Part 1: Definitions
RTO (Recovery Time Objective) and RPO (Recovery Point Objective) are application attributes highlighting an organization’s ability to recover an application to the customer or end user in the event of an unexpected outage.
RTO describes how long it will take to get an application online.
TechTarget Definition – The recovery time objective (RTO) is the maximum tolerable length of time that a computer, system, network, or application can be down after a failure or disaster occurs.
The RTO is a function of the extent to which the interruption disrupts normal operations and the amount of revenue lost per unit time as a result of the disaster. These factors in turn depend on the affected equipment and application(s). An RTO is measured in seconds, minutes, hours, or days and is an important consideration in disaster recovery planning (DRP).
Numerous studies have been conducted in an attempt to determine the cost of downtime for various applications in enterprise operations. These studies indicate that the cost depends on long-term and intangible effects as well as on immediate, short-term, or tangible factors. Once the RTO for an application has been defined, administrators can decide which disaster recovery technologies are best suited to the situation. For example, if the RTO for a given application is one hour, redundant data backup on external hard drives may be the best solution. If the RTO is five days, then tape, recordable compact disk (CD-R) or offsite storage on a remote Web server may be more practical.
RPO describes how far back in history the application or its data is allowed to be when that application comes back online.
TechTarget.com Definition – The recovery point objective (RPO) is the age of files that must be recovered from backup storage for normal operations to resume if a computer, system, or network goes down as a result of a hardware, program, or communications failure. The RPO is expressed backward in time (that is, into the past) from the instant at which the failure occurs, and can be specified in seconds, minutes, hours, or days. It an important consideration in disaster recovery planning (DRP).
Once the RPO for a given computer, system, or network has been defined, it determines the minimum frequency with which backup s must be made. This, along with the recovery time objective (RTO), helps administrators choose optimal disaster recovery technologies and procedures. For example, if the RPO is one hour, backups must be made at least once per hour. In this case, external, redundant hard drives may prove to be the best disaster recovery solution. If the RPO is five days (120 hours), then backups must be made at intervals of 120 hours or less. In that situation, tape or recordable compact disk (CD-R) may be adequate.
Simply put, RTO and RPO describe how long it will take to get an application back up, and at what point in history will the data be when the application is back up. The figure below is a visual representation of the description above. Assume ‘Now’ indicates the present time, or the time of an outage.
We will continue our explanation of RTO and RPO by introducing the concept of Service Level Agreements in Part 2 of this blog.
If you have any questions or comments for us about RTO and/or RPO or SLAs, please use the form below and we will get back to you with an answer.