Building a disaster recovery architecture with cloud and colocation

Last updated:November 2016

Editor's note

Viewed as a long-term IT insurance plan, disaster recovery has for years been a focal point for businesses. And, as more enterprise workloads move off-site, organizations are building a disaster recovery architecture with cloud and colocation to meet their specific needs.

But before getting started, evaluate the pros and cons of using cloud vs. colocation for disaster recovery, including geographic distance, business continuity options and overall costs.

Also, given the risks of outages and increased downtime that keeps IT out of the loop, it's important to plan and test your disaster recovery architecture -- whether using cloud, colocation or another model -- before a problem occurs. Learn from the mistakes of others and continuously improve your plan to meet the growing needs of the business.

1Manage disaster recovery policies and costs

Whether you use cloud or colocation for your disaster recovery architecture -- or even a secondary data center -- it's crucial to carefully review and manage DR policies, and to keep DR costs in check. Can costs be reduced with other measures, such as streamlined testing? What are your organization's recovery time objectives and recovery point objectives? Investigate where your DR strategy is working, and which areas can be boosted to create a safer plan in the event of a disaster.

2Big-name companies suffer big time after DR policies fail

Outages at companies including Delta Air Lines and Verizon shined a bright light on what happens to a business when its disaster recovery architecture fails. Learn how missteps ranging from a lack of redundancy to hardware failures can spark an outage -- and why a disaster recovery plan needs to be ironed out beforehand to prevent downtime.