Planning for High Availability
Configuring your servers for availability and reliability should be a continuing, evolving process that balances need and cost. This section discusses the concepts and technologies that help you design an available and reliable Communicator Web Access deployment, including failover mechanisms and load balancing. To plan a highly available network, you must consider more than just Communicator Web Access; however, only Communicator Web Access-specific considerations are discussed in this document. For example, this document does not discuss failure of the supporting components (such as DNS, Active Directory, Windows authentication, reverse proxies, load balancers, firewalls, Office Communications Server 2007, and the .NET Framework common language runtime) on which Communicator Web Access server relies. Total failure or lack of connectivity to any of these supporting components can result in degraded performance or loss of service.
For information about availability planning in general, see "Overview of Planning for High Availability and Scalability" at http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=PlanAvailScal.