Disaster-recovery plans fall short

By Ann Silverthorn

A survey of 500 IT managers conducted by Applied Research shows that nearly half of the companies do not have a disaster-recovery (DR) plan in place. Why? Lack of resources was cited by 33% of the respondents, while 27% don’t see a need for DR plans. The questions in the survey were designed to determine the level of IT organizations’ disaster-recovery readiness, deterrents to DR implementations, and future plans for DR and business continuity.

Even among companies that do have disaster-recovery operations in place, the implementations are often inadequate, according to Peter McKellar, a group product manager at Symantec, which commissioned the Applied Research survey. “Many companies need help from a technology perspective, but also from a process and people perspective,” he says.

Click here to enlarge image

“They may migrate all their servers and applications to a disaster-recovery site if an event happens, but they often don’t take into consideration who will operate those systems.”

Of those companies that have a disaster-recovery or business continuity plan in place, 61% cited data corruption as a primary motivating factor. McKellar says data corruption can come from a variety of sources, including human error as well as software or hardware failures. “Some sophisticated applications have multiple modules writing to the same file, which can cause conflict. A server can lose power in the middle of a file being written, or a hard drive can fail,” says McKellar.

Click here to enlarge image

Cost was mentioned most frequently (by 23% of the survey respondents) as the biggest challenge regarding disaster recovery and business continuity plans. In light of this statistic, McKellar notes that vendors and users have to come up with ways to make disaster recovery more cost-effective. One solution is to set up different levels, or tiers, for DR and business continuity. McKellar adds that it’s even possible to create tiers of availability within an application.

This article was originally published on March 01, 2006