High-availability architecture: Redundancy vs. abstraction

High-availability architecture: Redundancy vs. abstraction

As organizations become more dependent on their information systems, they begin to look for ways to make those systems more resilient. Data center managers have used focused on high-availability architecture for years, but the industry transition to virtual data centers has caused organizations to rethink their high-availability strategies.

    Requires Free Membership to View

    When you register, my team of editors will also send you the latest expert resources covering all areas of server virtualization, such as platforms, architectures and strategies, server hardware, managing virtual environments, application issues and more.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchServerVirtualization.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchServerVirtualization.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

One of the most interesting aspects of the shift to virtual data centers is that even small organizations that may never have used a clustering strategy are now almost forced to deploy some form of high-availability architecture. That's because smaller organizations often treat virtualization as a means to save money through consolidation.

But as organizations consolidate servers, they also consolidate risks. For example, an enterprise may not consider the failure of a single infrastructure server to be catastrophic. But the failure of a server that is hosting three or four virtual infrastructure servers would probably be a different story.

The problem is that unless an organization has a virtualization-specific strategy for its high-availability architecture, the failure of even a single server component can result in a major outage that affects a number of virtual servers. This is why it is so important to implement resiliency in even the smallest of virtual data centers.

Rethinking your high-availability architecture
There are two primary approaches to integrating resiliency into a virtual data center. One approach is to use redundant hardware. The other approach is to achieve resiliency through abstraction. Often these two approaches go hand in hand.

Redundancy within a virtual data center is similar to the various approaches to high-availability architecture that have been around for years. For example, an organization might use servers that have redundant components -- such as power supplies and network cards -- or they might deploy a clustering strategy. Although there really isn't anything wrong with redundancy, additional hardware can be expensive, and server clusters can be complicated and expensive to deploy and maintain.

Abstraction works by breaking all of the virtual data center's components into pieces and using management software to allocate those pieces. It's also important to know that there are different degrees of abstraction. Some virtual data centers may only perform hardware abstraction -- treating physical servers as a pool of resources -- while others might also abstract applications.

High availability through abstraction won't work without redundant hardware. Unlike more traditional hardware redundancy, though, abstraction-based high-availability approaches often use low-priced commodity hardware as opposed to specialized clustering solutions.

In part 2 of this tip, learn how to create a redundant network architecture.

 

Brien M. Posey, MCSE, has received Microsoft's Most Valuable Professional Award seven times for his work with Windows Server, IIS and Exchange Server. He has served as the CIO for a nationwide chain of hospitals and healthcare facilities and was a network administrator for Fort Knox. You can visit his personal website at www.brienposey.com.


This was first published in November 2010

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.