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
Business Pandemic Plan – Are You Prepared?
On June 11, 2009, the World Health Organization (WHO) raised the worldwide pandemic alert level to Phase 6 due to the spread of the H1N1 virus. The virus, also known as Swine Flu, has rapidly established itself and will continue to persist in the coming months as the...
NYSE in Chaos
A computer glitch stopped trading for 40 minutes in more than 200 stocks at the New York Stock Exchange today. One of the key computer servers used to conduct trading lost connectivity to the trading network. As a result, stocks such as General Electric and...
Terrorist Attacks – History Repeats Itself
In July of 1993, eight individuals were arrested and later convicted for plotting terrorist attacks on key sites in Manhattan. Such key sites included: the St. Regis, the Waldorf-Astoria and the UN Plaza hotels, as well as the Holland and Lincoln tunnels. VP of...
Airport Insecurity – Business Travelers Beware
As business begins to return to travel, there’s so much to consider when keeping yourself and your belongings safe. Working in airports has always been common practice, as is eating and drinking while working, but now there’s an additional layer of concern for...
0 Comments