Cost-cutting pressures on CIOs have led many to accept more risk and settle into a mindset that their Disaster Recovery (DR) program is comprehensive, when, in fact, it might not hold up when matched against the company’s business requirements.

Quite often, DR planning is not top of mind for senior management. With shrinking IT budgets and teams, keeping up with day-to-day responsibilities is challenging, and many IT teams will tend to focus on only the infrastructure, hardware, and software, while neglecting the people and processes that are needed to execute the plan. Introducing complexity into an IT business practice that is under-resourced can lead to an incomplete DR plan, failed recovery testing, or even worse, a company that has declared a disaster without any chance of recovering quickly.

To avoid failure, it is important to truly understand how your company addresses recovery management. In some instances, your IT teams may be reluctant to publicly identify areas of concern, while some may not even know whether their DR plan will work.

This checklist reveals 10 truths about DR that IT teams are most likely reluctant to tell their CIOs, and provides you with questions you can use to ask your team about your recovery management strategy.

DOWNLOAD 10 THINGS YOUR TEAM IS AFRAID TO TELL YOU ABOUT YOUR DR PLAN