DR and BC strategies hinge on IT and the business working together to test DR processes and procedures, ensuring that the most critical systems can get back up and running as quickly as possible. DR tests can be scheduled weeks, months or even a year in advance, depending on the systems or processes on hand. Kirvan highlights lack of preparation and not involving the pertinent players as major mistakes in a DR test plan.
While organizations can't anticipate the exact disaster they may be forced to confront, making sure that key players are aware of a disaster recovery test run gives them the opportunity to document how well -- or poorly -- it has been carried out. Added Kirvan:
And here's another – Not having the right players in attendance, e.g., wrong DBA, wrong net admin. #CIOChat— Paul Kirvan (@pkbcm1) June 25, 2014