New Study Finds That Only 54% of Organizations Have DR Plans in Place

iland has released the findings of its research into organizations’ disaster recovery readiness with some surprising results. “When Plan B Goes Wrong: Avoiding the Pitfalls of DRaaS” found that as organizations work diligently to support evolving business needs, while at the same time battling cybercrime and other threats to critical data, the majority of disaster recovery solutions are not tested on a regular basis.

More importantly, as the IT estate changes over time, the survey indicated most disaster recovery solutions would not meet recovery objectives.

The research surveyed 150 technical and business decision makers from organizations drawn from a wide cross-section of U.S. enterprises, each employing a minimum of 500 people. The objectives of the research were to establish what DR systems organizations currently have in place, how often plans are tested and whether enterprises are confident in their ability to recover from disaster as swiftly and easily as possible.

Key findings include:

Just over half (54 percent) of respondents had a documented, company-wide DR plan in place.
Failures and outages are more common than people realize. Seventy-three percent reported experiencing failure at some point. Almost two-thirds of that group had experienced the outage within the last 12 months and almost half of those within six months.
Fifty-seven percent have a second on-premise data center for DR purposes.
DR testing frequency is very low. Just 50 percent are testing only annually or at less frequent intervals, while seven percent did not test their DR at all.
Of the organizations testing less frequently, half said their disaster recovery plan may be inadequate based on their most recent DR test, while 12 percent encountered issues that would result in sustained downtime.
Zero respondents said that their DR test was completely or moderately successful. Everyone reported experiencing issues.
Of the issues experienced, most reported networking issues (67 percent), service unavailability (67 percent), data integrity problems (50 percent), application performance issues (50 percent) or missing critical workloads (50 percent).
Those testing more regularly are far more likely to have ambitious objectives for data recovery than those who test less frequently. Thirty-two percent expected to recover data in seconds or minutes and 23 percent actually did so.
Hardware failure represented the most frequently reported cause of a recent data recovery need, with 38 percent citing it.
The most frequently encountered problem with failback to original sites was networking problems, experienced by 62 percent.

Read more about the research findings here.