Avoid disaster with stretched clusters


Become An Insider

Sign up now and get free access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content from the best tech brands on the Internet: CIO, CSO, Computerworld, InfoWorld, IT World and Network World Learn more.

So-called stretched clusters promise utopia of disaster avoidance and disaster recovery virtualization, but the technology is still new. Here's how to deal with the challenges

Because virtualization offers so much cost savings and agility, many organizations are going the whole hog and virtualizing mission-critical systems they wouldn't have dreamed of virtualizing a little while ago. Who would have thought, for example, that we'd see enterprises deploy Oracle virtually rather than on physical hardware?

It's no surprise there's increasing interest in wringing every last drop of disaster recovery and disaster avoidance out of virtualization infrastructures. Most commonly, this is manifest in a replicated, dual-site architecture where virtualization resources can be quickly failed over to a secondary data center in the event that catastrophic failure strikes the primary site.

For some organizations, however, this isn't enough. They want the capability to seamlessly migrate workloads from one site to another in order to utilize computing resources at both sites. Moreover, they want the infrastructure to heal itself automatically in the event of a site or hardware failure -- just as single-site virtualization clusters are able to do. Hence the new buzz phrase "stretched cluster."

The stretched cluster has its challenges. But advances in the capabilities of virtualization stacks and the underlying storage gear have made so-called stretched clusters an increasingly attainable and attractive option.

To continue reading, please begin the free registration process or sign in to your Insider account by entering your email address:
From CIO: 8 Free Online Courses to Grow Your Tech Skills
View Comments
You Might Like
Join the discussion
Be the first to comment on this article. Our Commenting Policies