Why you should have a disaster recovery testing plan in place
A comprehensive collection of articles, videos and more, hand-picked by our editors
What are the most common mistakes you see when conducting DR testing?
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
This is by no means an exhaustive list, but typical mistakes include neglecting to do the following:
- Define the scope and objectives of the test.
- Develop a scenario for the test.
- Develop and document the test process.
- Alert other departments of the test.
- Define team responsibilities in the test.
- Ensure that all elements needed in the test, e.g., networks, databases, firewalls, load balancers, data, applications, hardware, have been prepared for the test.
- Contact all relevant test participants.
- Get approval for the test.
- Complete an after-action report on the test results.
- Update the DR plan based on test findings and lessons learned.
- Brief management on test outcomes.
- Schedule the next test.
Related Q&A from Paul Kirvan
When taking a hybrid disaster recovery approach -- using public and private components -- it's important to understand your requirements, assets and ...continue reading
If you're considering software-defined networking in your disaster recovery platform, define your DR requirements first. SDN can help support data ...continue reading
A call tree can be an important piece of disaster recovery planning. Follow these steps for call tree design and execution to ensure your company is ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.