BuckUP Lync2013. Часть 2. Восстановление.

С бэкапом мы разобрались в первой части, пришло время придумать как его восстановить.


Вариант первый.
Если сервера были забэкапированы по первому варианту описному в первой части, то нам понадобиться установочный диск. Грузимся с него выбираем восстановление, указываем путь где лежит иммидж диска и восстанавливаем. В принципе ничего сложного :).  Если возникнет интерес то это тема для отдельной статьи.
Вариант второй.
Устанавливаем все сервера с нуля. Адреса и имена серверов сохраняем теми же.
Затем устанавливаем необходимые компоненты.
для Windows Server 2012

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client, BITS -Source D:\sources\sxs

Add-WindowsFeature windows-identity-foundation

Восстанавливаем Central Management Store. На самом деле, это основной этап. На front-end-сервере устанавливаем компоненты администрирования Lync Server 2013: Topology Builder и одновременно установится модуль Powershell для Lync. Запускаем Powershell и импортируем модуль Lync.

Import-Module Lync

Install-CsDatabase -CentralManagementDatabase -Clean -SqlServerFqdn lync-be-13.domain.local -SqlInstanceName rtc -Verbose

Set-CsConfigurationStoreLocation -SqlServerFqdn lync-be-13.domain.local -SqlInstanceName rtc -Verbose

Импортируем CMS из бэкап-файла
Import-CsConfiguration -FileName D:\Backup\XdsConfig.zip

 И публикуем топологию

Enable-CsTopology

 PS

С сайта Microsoft
https://technet.microsoft.com/en-us/library/hh202171(v=ocs.15).aspx

Restoration

 To restore Lync Server, use the tools in the following table. All the commands that you need to restore Lync Server can be scripted. Some can be run remotely, but others need to be run locally, as specified in the following table.

Tools for Restoring Lync Server

To do this:	Use this tool or cmdlet:
Build a new or clean computer	Windows operating system installation software SQL Server installation software Certificates Microsoft Management Console (MMC) snap-in, if restoring certificates with an exportable private key
Restore file store data	Standard file system management tool, such as Robocopy
Recreate empty databases and set permissions for the following: Central Management store Back End Server Monitoring database Archiving database	Install-CsDatabase
Restore the Active Directory Domain Services pointer to the Central Management store Note: If you lose the service connection point at any time, you can rerun this cmdlet.	Set-CsConfigurationStoreLocation
Import the topology, policies, and configuration settings to the Central Management store (Xds.mdf)	Import-CsConfiguration
Publish and enable the topology	Topology Builder -or- Publish-CsTopology and Enable-CsTopology
Enable the last published topology	Enable-CsTopology
Reinstall Lync Server components	Lync Server Setup Note: Located in the Lync Server installation folder or media at \setup\amd64\Setup.exe.
Restore location information (E9-1-1) data (Lis.mdf)	Import-CsLisConfiguration
Restore persistent user data (Rtcxds.mdf)	Import-CsUserData
Restore Response Group configuration data (RgsConfig.mdf)	Import-CsRgsConfiguration Note: If the configuration is being restored in a newly deployed pool that has no Response Group data in the database, then you should use the –OverwriteOwner option. Use this option even if the data being restored is in a pool with the same fully qualified domain name (FQDN). Otherwise, the import will not succeed, due to the contact objects to the Response Groups already existing in Active Directory.
Restore the following databases: Archiving database (LcsLog.mdf) Monitoring databases: call detail record database (LcsCDR.mdf) and QoE database (QoEMetrics.mdf)	SQL Server database management tools
Persistent Chat database (Mgs.mdf)	SQL Server restore procedures or Import-CsPersistentChatData. You can use Import-CsPersistentChatData with a file created by Export-CsPersistentChatData, and the data will be imported into the Persistent Chat database.

Required Permissions

Users must be a member of the RTCUniversalServerAdmins group to perform all the commands described in this topic. Most backup and restore commands do not support role-based access control (RBAC). Two exceptions are the Persistent Chat cmdlets Export-CsPersistentChatData and Import-CsPersistentChatData, which must be run by a user who is a member of the CsPersistentChatAdministrator group. To run Lync Server Deployment Wizard, a user must also be a member of the Local Adminstrators group.