Topic Last Modified: 2011-03-03

If you require Microsoft Lync Server 2010 communications software to be always available, even in the event of a severe disaster at one geographical location in your organization, you can follow the guidelines in this section to create a topology that offers metropolitan site resiliency.

In this topology, Lync Server 2010 pools span two geographically separate locations. In such a topology, even catastrophic server failure in one location would not seriously disrupt usage, because all connection requests would automatically be directed to servers in the same pool but at the second location. The site resiliency solution described in this section is designed specifically for this split-pool topology and is supported by Microsoft subject to the constraints mentioned in Findings and Recommendations.

If your environment does not meet the requirements described in this document, For recommendations about providing resiliency for your Enterprise Voice workload, see Planning for Enterprise Voice Resiliency.

Unless specifically stated otherwise, all server roles have been installed according to the product documentation. For details, see Deployment in the Deployment documentation.

In This Section

  • This section does not include specific procedures for deploying the products that are used in the solution. Specific deployment requirements are likely to vary so much among different customers that step-by-step instructions are likely to be incomplete or misleading. For step-by-step instructions, see the product documentation for the various software and hardware used in this solution.

  • To successfully follow the topics in this section, you should have a thorough understanding of Lync Server 2010 and Windows Server 2008 R2 Failover Clustering.