5 Best Practices to Reduce Web 2.0 Risks

Jan 25, 2013


Costs Are Down, But Complexity Is Up

It wasn't so many years ago that InformationWeek surveys showed that barely a majority of respondents had and regularly tested disaster recovery plans. That's all changed -- the applications that IT fields are now central to the operation of most businesses, and downtime means money lost. Disaster recovery plans are now common, as is testing -- at least to some degree. The next step is to outline a set of manual steps and look at automating the process.

IT pros who did this analysis a few years ago came back with such pricey proposals that even the most even-keeled CFO's eyes bulged. From replication software to running systems in warm sites to bandwidth costs, bringing recovery times down from days to minutes would simply cost more than most organizations could justify.

Creating and implementing a one-click recovery plan is still not cheap, but it's far less expensive than it used to be. How critical are your applications? If the worst happens, is three days too long to wait for your apps to recover? Those who can't wait can often bring recovery times down to minutes with some new technology and careful engineering. (S6440113)

Research Report