It's no secret that building up effective disaster recovery (DR) capabilities is peppered with challenges. From identifying business requirements and mapping them to non-budget-busting technology solutions to coping with the operational impact of disaster recovery planning and testing, it seems that every step of the process introduces hurdles to overcome.
At the same time, surveys highlight that the increased impact of outages and business demand for improved uptime places more pressure on IT to do something to improve the state of disaster recovery within their organization(s). On the bright side, technology options for DR are increasing and becoming more and more cost-effective. The widespread adoption of server virtualization, an increased variety of options for networked storage and lower bandwidth costs are encouraging more organizations to renew their efforts to improve their DR practices. However, when trying to improve disaster recovery, there are steps that newcomers may miss and even old-timers may not adequately consider. So I've provided some of the best practices to help you avoid DR interdependency predicaments.