Manage Learn to apply best practices and optimize your operations.

Five common disaster planning and recovery pitfalls to avoid

6/6

Use disaster recovery examples based on real scenarios, not guesses

According to tweet jammer Ant Stanley, the No. 1 pitfall to avoid when doing a disaster recovery (DR) test is a lack of urgency and comprehensiveness. Others SearchCIO tweet jam participants agreed on the importance of grounding disaster recovery examples in real-world scenarios:

Andi Mann  may have said it best. Tweet jammers suggested that simulating real disaster scenarios helps organizations grow from DR tests, and in order to successfully test disaster recovery examples, you must get the business involved:

To prepare for a real attack, organizations and their CIOs must treat DR tests like a real attack. Other key takeaways from our #CIOChat-ters -- like planning to fail, scheduling tests in advance and documenting everything from beginning to end -- should guide your DR strategy as well.

For more disaster recovery resources, check out our CIO Essential Guide on disaster prevention and mitigation. For more on SearchCIO's #CIOChat, search the tweet jam hashtag on Twitter.

View All Photo Stories

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

What real-world disaster examples do you use when testing DR plans?
Cancel

-ADS BY GOOGLE

SearchCompliance

SearchHealthIT

SearchCloudComputing

SearchMobileComputing

SearchDataCenter

Close