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
Hurricane Impact Assessment: Isaac in New Orleans
Now that Hurricane Isaac is in our rear-view mirror, it’s time to assess the disaster damage. We monitored and shared the New Orleans power outages on Global Data Vault blog day-by-day, but we censored the wrath pointed at local energy provider Entergy to return the...
Loss of power during Hurricane Isaac
As Hurricane Isaac continues its slow march inland, the city of New Orleans is largely without power this afternoon. This image shows the widespread power outages in the city. It’s seems eerie that today is the seventh anniversary, if you should call it that, of...
How to build a disaster recovery site – part 3
Whether you are outsourcing your Disaster Recovery program or keeping it in house, the steps required to implement it are critical. In this series, we’ve drafted an outline of how to build a remote Disaster Recovery site for your IT. In our previous articles, Choosing...
Building a Disaster Recovery Site – part 2
What does it take to build a remote Disaster Recovery site for your IT? (Part 2 of 3) Whether you are outsourcing your Disaster Recovery program or keeping it in house, the steps required to implement it are critical. In this series, we’ve drafted an outline of how to...
0 Comments