Five common disaster planning and recovery pitfalls to avoid
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:
A2. Tough, so many possible pitfalls. Probably would say not following up and documenting failure resolutions. #CIOChat
— Andi Mann (@AndiMann) June 25, 2014
A2. Too many people consider that a 'fix'; but need to document, incorporate into standard procedure. #CIOChat
— Andi Mann (@AndiMann) June 25, 2014
A2: DR/BC testing will show results, good and bad, need to document it all to avoid problems next time #CIOChat
— Denise Dubie (@DDubie) June 25, 2014
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.
Join the conversation
2 comments
That makes detecting any problem much more easy and earlier.
If anyone interested on one of those tools have a look at Unitrends.