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:
— Ant Stanley (@IamStan) June 25, 2014
— Andi Mann (@AndiMann) June 25, 2014
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.