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 Continuity Planning – Vital Emergency Supplies
Vital Emergency Supplies There is never a good time for an emergency, but in the event of an untimely disaster your company must have much more than a basic first-aid kit on hand. In regard to emergency supplies, it's important to let workers know just what will be...
Business Continuity Risk Assessment
Preparing for Threats through Risk Assessment A successful business continuity plan involves preparing for the unexpected. No one ever wants to overindulge in negativity, yet it is only practical to be realistic in this day and age of untimely disasters. A major...
Budgeting for Disaster Recovery
Strategic budgeting ensures availability of essentials in the event of a disaster Understanding all the changes that could become an integral part of daily business operations is vital to the success of any business continuity plan. It is important for the management...
7.8 Magnitude Shakeout Earthquake Drill
What would you do if your neighborhood was struck by a 7.8 magnitude earthquake? Well, today the citizens of Southern California might have a better idea of what they would do after yesterday's United States Geological Survey's (USGS) shakeout earthquake drill. USGS...
0 Comments