Using a stretched Persistent Chat Server pool for disaster recovery in Lync Server 2013

 

Topic Last Modified: 2012-10-06

The disaster recovery solution for Persistent Chat Server is built on a stretched Persistent Chat Server pool. This is similar to metropolitan site resiliency in Lync Server 2010; however, there is no requirement for a stretched virtual local area network (VLAN). By stretching Persistent Chat Server pool, you essentially configure one pool in the topology logically, but you physically place the servers in the pool in two different data centers. Configure SQL Server mirroring for the database in the same way, and deploy the database and the mirror in the same data center. You need to configure a backup database in the secondary data center (with an optional mirror to provide high availability during disaster recovery). This is the backup database used for failover during disaster recovery.

For details about how to configure SQL Server mirroring for high availability, see SQL Server mirroring in Lync Server 2013. For details about failing over the database for disaster recovery, see Setting up SQL Server Log Shipping in Lync Server 2013 for the Persistent Chat Server primary database and Setting up SQL Server Log Shipping between the primary mirror and the Log Shipping secondary database in Lync Server 2013.