DRJ Fall 2019

Conference & Exhibit

Attend The #1 BC/DR Event!

Fall Journal

Volume 32, Issue 3

Full Contents Now Available!

Wednesday, 15 November 2017 21:56

Give Your RTO a Tune-Up By Asking These Four Questions


You are experiencing an outage. Servers have crashed, and your applications are unreachable. You have assessed that you cannot easily bring your production systems back up. You can’t quickly fix the production issue causing the outage either, and you need to spring to action with your disaster recovery plan. You have determined how long you will be offline by establishing your recovery time objective (RTO). This is a measure of how quickly you can recover or bring your applications back online after a disaster declaration. Based on how much downtime you can afford for an application, let us say your RTO is two hours. But what if it takes your team half an hour to find, dust off, and review the recovery plan that you have not tested or revised in years, and then you find out your infrastructure cannot support your plan? Recovery from that outage will be going way past