Cloud disaster recovery plan testing should include provider

Get your cloud DR test plan in order with this group of guidelines. Find out what your DRaaS vendor has to offer in terms of testing and how to make the most of it.

If your disaster recovery as a service vendor includes testing among its service offerings, find out early on how it will support your DR plan tests. Look for firms that offer unlimited testing, or a very liberal test policy, such as quarterly or bimonthly, so you can schedule as many tests as needed.

In addition, see what support the vendor offers for developing your cloud disaster recovery plan testing.

With regard to the testing process for disaster recovery as a service (DRaaS), or cloud DR, the following 20 best practices should ensure success.

  1. Determine what will be covered in your cloud disaster recovery plan testing, such as failover from production systems to the DR environment and failback from DR to regular production.
  2. Document the DR test plan, identifying who will be involved in the test and the resources you will need, such as virtualized systems, databases, and data and network services.
  3. Have your cloud disaster recovery plan reviewed in advance by the system and data owners to ensure that the plan's objectives are aligned with expectations.
  4. See if the DRaaS vendor will provide test scripts before you prepare your own.
  5. Prepare test scripts to facilitate the test. This is essential, as the scripts will be validated in the test and will serve as your procedures in an actual emergency that requires the use of your DRaaS vendor.
  6. Determine the level of support you can expect from the DRaaS vendor; for example, on-site monitoring of your testing progress vs. remote monitoring via a conference bridge, and technical support as needed.
  7. Ensure all the resources required for the test are working properly.
  8. Notify other departments in your organization -- especially within IT -- of your proposed disaster recovery plan testing. Notify senior management of your planned test, including what will be tested and the expected results.
  9. Discuss disaster recovery plan testing activities with all the members of the test team in advance so each person knows their role and responsibilities during the test.
  10. If it can be scheduled, and if your DRaaS vendor supports it, schedule a dry run of the test with as many participants as possible, including the vendor. This may uncover problems -- for example, incorrect scripts, incorrect URLs or other resources -- that could adversely affect the success of your DR test.
  11. Ensure the test is conducted in an environment that will not affect ongoing production systems, such as in research and development or a system testing environment.
  12. Once the cloud disaster recovery plan test commences, have someone take notes and keep time of the testing activities. Test script documents should have places to enter notes and to record times when specific activities are completed.
  13. Schedule a break in the test to examine how it is progressing; but remember, you won't have that option in a real emergency. Be prepared to halt the test if activities are not completing as planned.
  14. Once the test has completed and the results have been documented, conduct a debriefing to see what worked, what didn't work and what remediation is needed for activities that failed.
  15. Document an after-action report for the test and submit it to management.
  16. Review disaster recovery plan testing results with your DRaaS vendor to see how it can assist you with resolving any issues.
  17. If possible, conduct another test to see if the revised test plan and scripts result in a successful test. If another test is not possible, examine the risk to the organization if the issues uncovered in the test actually occurred during a real emergency. All findings should be noted in the after-action report or a subsequent post-test report.
  18. If the systems and resources are mission-critical, perform additional testing to ensure those assets can be recovered.
  19. Update the disaster recovery plan and any other documents based on the test results.
  20. Coordinate with your DRaaS vendor to schedule the next round of tests.

When you have a DRaaS vendor that recognizes the importance of cloud disaster recovery plan testing, you are much more likely to have a successful recovery when it's needed.

Next Steps

12 steps for a successful DRaaS implementation

Do DRaaS providers have an issue with cloud bandwidth?

DRaaS vs. cloud DR: What are the differences?

Dig Deeper on Cloud disaster recovery