Manage Learn to apply best practices and optimize your operations.

Five common disaster planning and recovery pitfalls to avoid

5/6

Don't forget to document DR test results with an after-action review

Documenting test runs of disaster recovery (DR) plans with an after-action review will not only improve future tests, but set your organization up for success when real disaster strikes.  

#CIOChat participant and Forrester alum Rachel Dines, now a product marketing manager at Riverbed Technology, was the first to advocate for the importance of an after-action review during SearchCIO's disaster recovery-themed tweet jam. Dines was quickly backed by other tweet jammers who agreed that, by not following up, organizations are increasing the likelihood of DR snags in the future:

Making documentation standard procedure, as Andi Mann suggested, will ensure that your organization is learning what works and what doesn't in its DR plan. In order to obtain proper documentation, key players must be involved in the DR test and must treat it like a real disaster.

View All Photo Stories

Join the conversation

2 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Does your organization conduct after-action reviews following DR plan test runs?
Cancel
There are tools that automate running daily DR tests and report DR results on virtualized enviroments.

That makes detecting any problem much more easy and earlier.

If anyone interested on one of those tools have a look at Unitrends.
Cancel

-ADS BY GOOGLE

SearchCompliance

SearchHealthIT

SearchCloudComputing

SearchMobileComputing

SearchDataCenter

Close