Important points related to Disaster Recovery and Business Continuity

These phrases are frequently used in Disaster Recovery (DR) and Business Continuity (BC), or high availability (HA).

Recovery Point Objective (RPO)
Recovery Point Actual (RPA)
Recover Time Objective (RTO)
Recovery Time Actual (RTA)

It’s simple to mix up these acronyms because they are so similar to one another. Here is a primer on the meaning of each of these phrases and how to use them to plan for BC, DR, and HA.

Recovery Point Objective (RPO) – How much data are you prepared to lose?

The amount of current data that the company is willing to risk in the event that the production source system is down is determined by the RPO.
If you ask a company how much data loss they can stand in the event of a disaster, they’ll probably say zero. The conversation will likely shift to defining how many hours of data they can afford to lose and defining multiple RPO tiers that will apply to IT services depending on the service and business impact once you have explained to them how expensive and challenging it is to try to achieve a zero RPO for all IT services.
RPO is a business requirement that specifies the BC/DR plan that IT must deploy to comply with RPO. A lack of business and IT alignment may have disastrous effects and have a negative influence on the company.

How can I ensure that I am always compliant, then? keeping an eye on your RPA and reporting any differences between the actual and desired values.

Recovery Point Actual (RPA) – How much actual data may be lost and yet be in compliance?

RPA is a measure that shows how much actual data would be lost if a disaster occurred right now and a restore from a local or offshore backup was required.

RPA must always be less than your RPO in order to be in compliance with your RPO policy at any given time.

Recover Time Objective (RTO) – How long do you think your recovery will take?

How rapidly you can switch from your production source system to your target backup machine in an emergency is referred to as a recovery time objective (RTO). An RTO is a target, not a statistic, much like your RPO is. It outlines your objectives for resuming the system on a backup machine or partition in the event of a significant outage on a production box. Depending on the BC/DR/HA system you’re utilizing, your RTO may change.

The cost to run a BC/DR/HA system in an emergency is inversely correlated to the cost to implement that same solution. Your choice of solution will be impacted by an RTO, which is a business choice.

Choose your RTO wisely and be aware that it is directly related to how patient your business or client is with service restoration during an outage.

Recovery Time Actual (RTA) – How long does it actually take to recover your system?

Recovery Time Actual (RTA) measures the length of time it actually takes for your BC/DR/HA system to activate in a crisis.

An RTA IS a statistic, in contrast to the RPO and RTO, which are goals.

If your target system goes down for any reason, your RTA serves as the baseline for how long it actually takes to restore production to that system.

You can gauge the success of your switch strategy using the RTA. Having an RTA necessitates testing your switch strategy because it can only be computed during a real switchover.

Your switchover strategy needs to be revised if there is a sizable difference between your RTO (objective) and RTA (actual), in order to reduce the time it takes to switch production from source to target.

Another thing to keep in mind is that by doing routine switch tests, you can evaluate the efficacy of your RPO (how tightly your source and target machine data are in sync).

Combining RPOs, RTOs, and RTAs

These three figures, when combined, serve as management jargon for the effectiveness of your BC/DR/HA solution.

How closely source and target machine data are synchronised is determined by the RPO. You must determine how much data will be lost if your production vanishes overnight. RPO needs to be monitored both when replicating and switching production.

In the event of a catastrophic failure, the RTO specifies your desired aim for how quickly production may be transferred to a target machine.

The RTA is your BC/DR/HA solution’s real performance in moving production to a target system in the case of a failure. To validate your RTO, it needs to be tested frequently.

Your RPO, RTO, and RTA are useful management tools for conveying your goals for your solution and how well you are performing in meeting those goals when they are properly stated.

How Can ITM Help You?

IT Minister covers all aspects of Cyber Security including but not limited to Home cyber security managed solutions to automated manage Threat Intelligence, Forensic Investigations, Mobile Device Management, Cloud security best practice, Enterprise Network & Security Architecture, Application Security Testing and Cyber Security training. Our objective is to support organisations and consumers at every step of their cyber maturity journey. Contact Us for more information.


Leave a Reply

Your email address will not be published. Required fields are marked *