Accessibility

Breeze Article

Clustering Breeze Servers with Microsoft Network Load Balancing


Frank S. DeRienzo Sorry, this page is not available

Table of Contents

Created:
9 November 2005

Many software-based server load-balancing and failover options have prematurely reached the end of the product life cycle. The market prediction that effectively swept software-based options off the enterprise landscape was that the price of superior hardware-based solutions would decrease enough to make the software options superfluous. The problem with this prediction is obvious to anyone who has tried to cluster a small pool of application servers on a tight budget: the price of the hardware options that are worth having have not dropped enough to fill the niche occupied by software clustering applications.

While the hardware-based options are more robust, the niche for software options remains even while options have diminished. The key player left in this field of diminishing options is Microsoft Network Load Balancing (NLB); it is built into the Microsoft Windows 2003 server TCP/IP stack as a standard option. If configured properly, NLB can be used to cluster a pool of Breeze servers and provide a means of IP-based failover. This article describes how to use NLB to cluster a pair of Breeze servers running Macromedia Breeze Meeting with a full suite of Breeze options.

Requirements

To understand this article, you’ll need:

  • Basic networking skills
  • Familiarity with the Windows server IP stack and NLB
  • Skill with DNS name resolution

Note: This article is intended as a Breeze supplement to the NLB documentation provided by Microsoft; it is not exhaustive and does not serve as a replacement for NLB documentation. For details on NLB, see the Windows Server 2003 Network Load Balancing (NLB) Technical Library. This article is also a supplement to the Breeze Installation and Configuration Guide, and as such does not provide all the information needed to fully install and configure Breeze.

About the author

Sorry, this page is not available