This is how I’ve done it. First in lab then in production. This is moving enterprise edition databases. For this to work you need one extra temporary sql server and one Lync server in a temporary Lync pool ,along with the new SQL production server.
| 1. | Export Lync configuration just in case. export-csconfiguration -file c:\lyncconfig.zip export-cslisconfiguration -file c:\lynclisconfig.zip |
| 2. | Install a new Lync server in a new pool. I.e temppool.corp.local |
| 3. | Install a new CMS (configuration management store) on temporary sql server. install-csdatabase -CentralManagementDatabase -sqlserverfqdn tempsql.corp.local |
| 4. | Enable topology. enable-cstopology |
| 5. | Logon to new server in new pool and move CMS Lync server. move-csmanagementserver Verify that you are moving it to the new server and select. Get-csmanagementreplicationstatus Wait for replication. |
| 6. | Uninstall old CMS database. Uninstall-csdatabase -CentralManagementDatabase -sqlserverfqdn OLDSQLSERVERFQDN.corp.local |
| 7. | Backup Lync databases. All of them. |
| 8. | In topologybuilder create a new sql server at the enterprise pool properties and publish topology. |
| 9. | Run Lync server setup deployment wizard. |
| 10. | Turn off all Lync frontend servers. |
| 11. | Restore Databases to the newley created databases. Remember to enable Chaining on the RTC and RTCDYN databases. Enable cross database chaining in the sql server properties. (SQL 2008 R2) In SQL-query : alter-database rtc set db_chaining = on alter-database rtcdyn set db_chaining = on |
| 12. | Start Lync servers. |
| 13. | Mover CMS to new SQLserver. step 1 – 6 |
| 14. | Delete temppool from topologybilder and publish. |
