Deploying Paired Front End Pools for Disaster Recovery
Lync Server 2013
Topic Last Modified: 2013-02-21
You can easily deploy the disaster recovery topology of paired Front End pools using Topology Builder.
If the pools are new and not yet defined, use Topology Builder to create the pools.
In Topology Builder, right-click one of the two pools, and then click Edit Properties.
Click Resiliency in the left pane, and then select Associated Backup Pool in the right pane.
In the box below Associated Backup Pool, select the pool that you want to pair with this pool. Only existing pools that are not already paired with another pool will be available to select from.
Select Automatic failover and failback for Voice, and then click OK.
When you view the details about this pool, the associated pool now appears in the right pane under Resiliency.
Use Topology Builder to publish the topology.
If the two pools were not yet deployed, deploy them now and the configuration will be complete. You can skip the final two steps in this procedure.
However, if the pools were already deployed before you defined the paired relationship, you must complete the following two final steps.
On every Front End Server in both pools, run the following:
<system drive>\Program Files\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
From a Lync Server Management Shell command prompt, run the following:
Start-CsWindowsService -Name LYNCBACKUP
Force the user and conference data of both pools to be synchronized with each other, with the following cmdlets:
Invoke-CsBackupServiceSync -PoolFqdn <Pool1 FQDN>
Invoke-CsBackupServiceSync -PoolFqdn <Pool2 FQDN>
Get-CsBackupServiceStatus -PoolFqdn <Pool1 FQDN>
Get-CsBackupServiceStatus -PoolFqdn <Pool2 FQDN>
|The Automatic failover and failback for Voice option and the associated time intervals in Topology Builder apply only to the voice resiliency features that were introduced in Lync Server 2010. Selecting this option does not imply that the pool failover discussed in this document is automatic. Pool failover and failback always require an administrator to manually invoke the failover and failback cmdlets, respectively.|