Many organizations have annual disaster recovery (DR) test requirements, whether to run production operations from a secondary facility for several days or test the functionality of systems and applications running in a DR facility while production workloads run as usual. Every business should have a disaster recovery plan and perform a DR test, especially with recent virus and ransomware activity.
In the past, disaster recovery was much more complex. However, virtualization and cloud technologies significantly improved DR capabilities and the ability to run workloads in separate or multiple locations. While advantageous, it is crucial to check the functionality of systems, processes, and people resources.
How often should I perform a disaster recovery test?
Your business needs and requirements will determine the testing frequency, but an annual test is usually sufficient for many. It is essential to schedule the test well in advance, especially if it involves a third party. Finding time for all parties as the end of the year approaches will be difficult. If you make significant infrastructure or application changes, it may be worth performing an additional test.
What are the goals of a disaster recovery test?
While you may think the goals of a DR test are obvious, setting objectives helps keep tasks in scope and focused. Implementing a disaster recovery testing plan helps. You want to verify connectivity and application functionality and ensure you have the appropriate users available to assist. Believe it or not, running into problems during your DR test can be a good thing so you can resolve the issues. You do not want to encounter issues during an actual emergency!
Some issues we have discovered while performing DR tests for customers:
- Old, unsupported, or end-of-life operating systems
- Unsupported operating systems that are too new (beta, just released)
- Old versions of virtual machines and hypervisors
- Unpatched servers take a long time to bring up, as they apply patches automatically. (Note: Be sure to follow regular patching practices.)
- Incomplete networking documentation
Disasters can happen at any time. Performing a disaster recovery test allows organizations to prepare ahead of a crisis and remediate issues before a disaster occurs. In addition to applications and systems testing, tests will enable you to fine-tune call trees, identify application owners and stakeholders, and understand the process of turning on DR workloads.
More Disaster Recovery Articles
What went wrong in the days before Super Storm Sandy?
“Not only were many firms unsure about whether their galoshes were waterproof,” Bart Chilton, the regulator at the Commodity Futures Trading Commission said, “they hadn’t even tried them on.” Chilton’s sharp-tongued critique is in response to the apparent lack of...
Data Center Exposure and Recovery in New York City
Hurricane Sandy provided a fascinating opportunity to study the both the level of disaster planning and the resilience of New York City data centers. This article will examine a) what actually happened, b) what was the risk, and c) what are the lessons learned. What...
Data Protection Audit – Systems, Devices and IT Operations
Your data protection audit lays out the plan that enables you to sleep at night knowing that data loss couldn’t destroy your business or be a costly and burdensome event. In the previous installment of our three part data protection audit series, we looked at the...
Data Protection Audit Planning
In part one of “How to plan and execute a data protection audit,” we discussed the importance of user participation in the design process of your data audit plan. In this installment, we go into more detail about the questions you need to ask about your business...
0 Comments