Topic Last Modified: 2011-03-02

The metropolitan site resiliency solution described in this section entails the following:

The following figure provides an overview of the resulting topology.

With the topology depicted in the preceding figure, a single site could become unavailable for any reason, and users would still be able to access supported unified communications services within minutes rather than hours. For a detailed depiction of the topology used to test the solution described in this section, see Site Resiliency Topology.

Scope of Testing and Support

This site resiliency solution has been tested and is supported by Microsoft for the following workloads:

  • IM and presence

  • Peer-to-peer scenarios; for example, peer-to-peer audio/video sessions

  • IM conferencing

  • Web conferencing

  • A/V conferencing

  • Application sharing

  • Enterprise Voice and Telephony Integration

  • Enterprise Voice applications, including Conferencing Attendant, Conferencing Announcement service, Outside Voice Control, and Response Group service

  • Approved unified communications devices

  • Simple URLs

  • Group Chat

  • Exchange UM

Workloads That Are Out of Scope

The following scenarios can be deployed in the metropolitan site resiliency topology, but the automatic failover of these workloads is not designed or supported:

  • Federation and Public IM Connectivity

  • Remote call control

  • Microsoft Lync Web App

  • XMPP Gateway