Do-It-Yourself: Risk Profile and Economic Value of Protection Self-Assessment for Disaster Recovery
Thinking about disaster recovery can be emotional for even the most technical professional. DR starts to examine uncertainties and likelihoods and forces the business to examine the worst-case scenarios and then match those against money that could be spent on development instead of the “just-in-cases”.
What is Disaster Recovery (DR)?
DR is the process of getting the service tools back up and running to provide service. In the IT world, that DR plan is how to get your applications recovered and up and running at 100% after a disaster impedes their function.
Benefits of this Self-Assessment to Determine Your Risk Profile and Economic Value
- Identify Gaps – You may be protecting yourself against the wrong potential disaster. When it comes down to protection you should be most worried about three types of disruption timeframes: single day, multi-day and prolonged length.
- Disruptions – Threats to the business infrastructure occur in three major categories: human error, geographic and infrastructure. The first category includes mistakes, malicious attacks and lack of knowledge mistakes. This self-assessment will help you understand your vulnerabilities for each category.
- The Business Case – Your DR budget, no matter how small, does need to come from somewhere. By using the economic value of protection formula in this self-assessment, you will be able to walk in to the CFO’s office and you’ll be speaking their language.
Disruptions Shorter Than One Day in Length
Disruptions that last less than one day can often be recovered from high availability set-ups and backups. Short disruptions are the most likely disruptions to occur in any environment, be it cloud, physical or virtual. Guard against these inconveniences in your set-up and backups and let your DR plan help you through the real concerns.
DR Planning Considerations
Testing should occur early and often. A common misconception is that you only need to test once successfully and then you’re done testing.
Your application is likely to change a significant amount over the course of a calendar year. A static DR plan will likely be less successful in recovery compared to one that is tested at least bi-annually. Testing is not just about making sure a proper failover will happen, but it’s also about identifying and compensating for changes that have happened since your last test.
What is Cloud-Based DR?
With cloud-based Recovery-as-a-Service (RaaS) solutions, testing is easy and affordable. Your DR solution is only as good as its ability to recover when you need it. And with cloud-based RaaS, you’ll have the confidence only frequent testing can provide to know you will be able to recovery quickly and easily when you need to most.