We were in transition phase to move CMS database from lync 2010 to Lync 2013 server. All users were migrated and now migrating CMS.
Lync 2010 Environment:
Lync 2010 Front End Pool contain two front end servers and one of the front end server is CMS master Server. This pool has one standalone SQL server which is holding CMS database along with other database.
Lync 2013 Environment:
Lync 2013 have three front end servers. This front end pool have two node cluster SQL which is holding backend datasbe for this pool. Backend SQL cluster is also holding instance for one other front end pool called “BIG Meeting”.
As per MS article we issues the below command to create the new Central Management store database in the Lync Server 2013 SQL Server database which is a prereqsuite to start the CMS realocation
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn “FQDN SQLInstance” -SqlInstanceName “SQLInstance”
Above command failed with below error
Install-CsDatabase : Command execution failed: The requested object does not exist. (Exception from HRESULT: 0x80010114)”
Solution: As we have SQL cluster hosting all lync 2013 BE instance, we must use database and log file path to tell the cmdlets to create CMS database.
Then we used a command as below with ‘DatabasePaths’ switch.
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn “FQDN SQLInstance” -SqlInstanceName “SQLInstance” -DatabasePaths “E:\CSLog”,”F:\CSLog”,”G:\CSDB”
This command was able to successfully created the xds database.
We also move the CMS from Lync 2010 to Lync server 2013 pool, it was completed successfully.
Hope it will help others hosting Lync 2010/2013 database in SQL cluster form 🙂 !!!
Configure SQL Server clustering for Lync Server 2013
Database installation using Lync Server Management Shell in Lync Server 2013