Hello. I know this has been done many tines before, but I thought I would share some notes and procedures on failing over\back an Microsoft Lync 2013 pool and testing\verifying the failover. This post is very much inspired by the same section in Matt Landis’ “Microsoft Lync Server 2013 Step By Step for Anyone eBook”. Thanks @mattlandis_gp !

 Basic design is 2 Lync 2013 pools in different data-centers, configured as backup partners.

“Normal” State:

  • CMS is homed in Datacenter DC1 Pool : lync2013pool01.contoso.com
  • Backup Pool relationship with DC2 Pool : lync2013pool02.contoso.com
  • Each regional Pool has the following Edge pool relationship:

lyncedgepool.contoso.com next hop of Lync2013pool01.contoso.com

lyncedgepooleu.contoso.com next hop of Lync2013pool02.contoso.com

Verify status

  1. Verify location of the active CMS :

Get-csservice –centralmanagement



Invoke-csmanagementserverfailover –whatif (Use whatif here. Without and “You’re fired” 🙂 Run from backup pool)


1. Verify backup Pool for CMS :

Get-cspoolbackuprelationship –poolfqdn lync2013pool01.contoso.com


 2. Verify availability of CMS pool : 

Get-csmanagementstorereplicationstatus –centralmanagementstorestatus


3. Verify Central Management Store replication:




1. Fail Edge pool (if applicable aka you have an Edge :))

If a Front End pool fails but the Edge pool at that site is still running, you must know whether the Edge pool uses the failed pool as a next hop pool. If it does, you must change the Edge pool to use a different Front End pool before failing over the failed Front End pool. In other words, if DC1 pool lync2013pool01.contoso.com fails but the local edge pool lyncedgepool.contoso.com is still available, it must be configured to use DC2 pool lync2013pool02.contoso.com. The opposite would be true if the DC2 pool were to fail to DC1. In a total site failure this is not necessary.

Set-csedgeserver –identity edgeserver:lyncedgepool.contoso.com –registrar registrar:lync2013pool02.contoso.com


2. Fail CMS

From a front end in the available pool:

Invoke-CsManagementserverfailover –backupsqlserverfqdn SQLMIRROR001.contoso.com –backupsqlinstancename lync -force


3. Verify CMS move by running:

Get-csmanagementstorereplicationstatus –centralmanagementstorestatus (this may take serveral minutes to populate after running). Note that the ActivemasterFQDN and ActiveFileTransferAfentFQDN are pointing to DC1 Front Ends.


4. Fail users to backup pool :

Invoke-cspoolfailover –poolfqdn lync2013pool01.contoso.com –disastermode –verbose


I just love  the ‘Hydrating’ bit. 🙂



The process is generally the same to fail back to the “original” pool but only in the other direction. 


1. Restore services to failed datacenter and ensure Lync 2013 is functional.

2. Invoke-CsBackupServiceSync –poolfqdn lync2013pool01.contoso.com (or applicable pool)

3. If required to move CMS back to original pool, this should be done first though it is not required to move the CMS back to the original location.

4. Invoke-CsPoolfailback –poolfqdn lync2013pool01.contoso.com –verbose to fail the users back to the original pool

5. Revert Edge topology changes

Set-csedgeserver –identity edgeserver:lyncedgepool.contoso.com –registrar registrar:lync2013pool01.contoso.com


I hope this is useful and as always please comment if you see something that could be added or changed.