How To Beat 3 Disaster Recovery Roadblocks - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Cloud // Cloud Storage

How To Beat 3 Disaster Recovery Roadblocks

Don't let data, WAN and integration challenges knock automated failover off course.

InformationWeek Green - Feb. 20, 2013
InformationWeek Green
Download the entire InformationWeek February special issue on disaster recovery, distributed in an all-digital format as part of our Green Initiative
(Registration required.)


3 Disaster Recovery Roadblocks

Not so long ago, InformationWeek surveys showed that many companies' disaster recovery plans were largely incomplete and unproven. For example, among 420 respondents to our 2011 Backup Technologies Survey, just 38% tested their restoration processes at least once a year for most applications. Only half backed up all their virtual servers every week.

Since then, things have improved, particularly the technology. This shift has come about because the applications that IT fields are increasingly central to business operations, and downtime means serious money lost. That translates into budget for business continuity and disaster recovery programs. Eighty percent of respondents to our new InformationWeek 2013 State of Storage Survey have strategies in place, and half of them test regularly.

The next step is to automate the process of failing over to a warm backup site -- one where hardware is up and running and data is regularly replicated from the production site. Removing people from the equation streamlines the process and lessens the possibility of error and costly delay.

We realize that many IT pros who priced an automation project just a few years ago came away with sticker shock. Between replication software, running systems in warm sites and bandwidth costs, bringing recovery times down from days to minutes costs more than most companies could justify. Implementing an automated recovery plan still isn't inexpensive, but prices have come down enough that, with some new technologies and careful engineering, we can often bring recovery times down to minutes for a reasonable price; we discuss some of these in our report on BC/DR and the cloud.

But while tech advances have handed IT pros a plethora of new tools to streamline failover to a warm site, complexities remain. Three areas in particular can derail automated disaster recovery: not having complete data sets in place for critical applications, a lack of bandwidth and incomplete integration.

Fresh, Hot Data

Report Cover
Our full 2013 State of Storage report is free with registration. This report includes 53 pages of action-oriented analysis, packed with 45 charts.

What you'll find:
  • Technology and software trends
  • Six recommendations for the year ahead
Get This And All Our Reports

Getting an application up quickly at a warm site means that its data must be there, ready and waiting. In manual failover scenarios, data can be a little dated: A stakeholder decides on reasonable RPO and RTO (recovery point and recovery time objective) metrics and agrees that some data might be lost. But for automated recovery of applications to work, completeness and integrity of the data at the recovery site are critical.

Primary array replication is the best way to mirror data from one site to another without human involvement. However, the licensing and storage costs associated with replication have tabled many a failover project. In the last couple of years, we've seen a number of changes: The commoditization of enterprise storage, the emergence of upstart providers of appliances and software, and the introduction of managed replication services have dramatically driven down the cost, regardless of the platform or technique used. In fact, our State of Storage report shows the percentage of respondents using replication on a widespread or limited basis ticked up three points since last year, to 70%.

But replicating data to a warm site still requires bandwidth, and plenty of it, which brings us to our second roadblock.

To read the rest of the article,
download the InformationWeek February special issue on disaster recovery

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Slideshows
7 Technologies You Need to Know for Artificial Intelligence
Jessica Davis, Senior Editor, Enterprise Apps,  7/1/2019
Commentary
A Practical Guide to DevOps: It's Not that Scary
Cathleen Gagne, Managing Editor, InformationWeek,  7/5/2019
Commentary
Diversity in IT: The Business and Moral Reasons
James M. Connolly, Editorial Director, InformationWeek and Network Computing,  6/20/2019
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
A New World of IT Management in 2019
This IT Trend Report highlights how several years of developments in technology and business strategies have led to a subsequent wave of changes in the role of an IT organization, how CIOs and other IT leaders approach management, in addition to the jobs of many IT professionals up and down the org chart.
Slideshows
Flash Poll