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
Carbonite Data Loss – Our Analysis
The Boston Globe and other outlets reported this weekend that Carbonite lost data for 7,500 customers. Many of these customers were able to make fresh backups before they suffered any real losses. Some, however, were not. Those who were not recieved apologies and...
What Happened to Ma.gnolia? The Autopsy
Larry Halff’s social media website ma.gnolia.com is gone. He spent four years during which he, “devoted most of my time, energy, and love” to building the site. Users of the site had built intellectual and social capital through the bookmarks, groups, and connections...
Business Continuity Planning – Internet Security
Practicing Internet Security Security is an issue for almost every computer user, especially those who frequently use the internet. Computers have become an integral part of everyday life and act as the lifeblood for many critical business operations. It doesn’t...
Congratulations Due at Fannie Mae
USA Today is reporting that a plot to destroy data at Fannie Mae was uncovered and is being prosecuted. In this case it was a fired employee named Rajendrasinh Makwana. His plan was to insert a virus to attack and destroy data at the government chartered mortage...
0 Comments