Share via

  • Article

Restoring the Central Management Store

 

Topic Last Modified: 2012-01-17

A Microsoft Lync Server 2010 deployment has a single Central Management store, a copy of which is replicated to each server running a Lync Server 2010 server role. This section describes how to restore a Back End Server or Standard Edition server that hosts the Central Management store.

To find the pool where the Central Management Server is located, open Topology Builder, click Lync Server 2010, and look in the center pane under Central Management Server.

Note

If a Back End Server or Standard Edition server that does not host the Central Management store failed, see Restoring an Enterprise Edition Back End Server or Restoring a Standard Edition Server. If any other server failed, see Restoring an Enterprise Edition Member Server.

Before you restore user data, you need to verify that user replication is complete. If user replication is not complete, Dbimpexp.exe will fail. This section describes how to verify that user replication is complete.

Tip

We recommend that you take an image copy of the system before you start restoration so that you can use this image as a rollback point in case something goes wrong during restoration. You might want to take the image copy after you install the operating system and SQL Server, and restore or re-enroll the certificates.

To restore the Central Management store

  1. Start with a clean or new server that has the same fully qualified domain name (FQDN) as the failed computer, install the operating system, and then restore or re-enroll the certificates.

    Note

    Follow your organization's server deployment procedures to perform this step.

  2. From a user account that is a member of the RTCUniversalServerAdmins group, log on to the server you are restoring.

  3. If you are restoring a Standard Edition server, restore the File Store by copying the appropriate File Store from $Backup to the File Store location on the server, and then share the folder.

    Important

    The path and file name for the restored File Store should be exactly the same as the backed up File Store so that components that use the files can access them.

  4. Do one of the following:

    • If you are installing a Standard Edition server, browse to the Lync Server 2010 installation folder or media, and start the Lync Server Deployment Wizard located at \setup\amd64\Setup.exe. In the Deployment Wizard, click Prepare first Standard Edition server and follow the wizard to install the Central Management store.

    • If you are installing an Enterprise Back End Server, install SQL Server 2008 R2, SQL Server 2008, or SQL Server 2005, keeping the instance names the same as before the failure.

      Note

      Depending on the server you are restoring and on your deployment, the server might include multiple collocated or separate databases. Follow the same procedure to install SQL Server that you used originally to deploy the server, including SQL Server permissions and logins.

  5. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  6. Recreate the Central Management store. At the command line, type:

    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn <FQDN> -SqlInstanceName <instance name> -Verbose

    For example:

    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn Server01.contoso.com -SqlInstanceName cms -Verbose

  7. Set the Active Directory service control point for the Central Management store. At the command line, type:

    Set-CsConfigurationStoreLocation -SqlServerFqdn <FQDN> -SqlInstanceName <instance name> -Verbose

    For example:

    Set-CsConfigurationStoreLocation -SqlServerFqdn Server01.contoso.com -SqlInstanceName cms -Verbose

    Note

    If you lose the connection point, you can rerun this cmdlet.

  8. Import the Central Management store data from $Backup. At the command line, type:

    Import-CsConfiguration -FileName <CMS backup file name>

    For example:

    Import-CsConfiguration -FileName "C:\Config.zip"

  9. Enable the changes you have just made. At the command line, type:

    Enable-CsTopology

    Note

    After you enable the topology, you can find the topology document in the database.

  10. Publish the topology by doing the following:

    1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.

    2. Click Download Topology from existing deployment, and then click OK.

    3. Select the topology, and then click Save. Click Yes to confirm your selection.

    4. Right-click the Lync Server 2010 node, and then click Publish Topology.

    5. Follow the Publish the Topology wizard. If you are restoring a database other than the Central Management store on this server, on the Create databases page, select the databases you want to recreate.

      Note

      Only stand-alone databases are displayed on the Create databases page. Collocated databases are created when you run the Lync Server 2010 Deployment Wizard.

    6. Follow the rest of the wizard, and then click Finish.

    Tip

    Instead of running Topology Builder, you can use the Install-CsDatabase cmdlet to create each database. For details, see the Lync Server Management Shell documentation.

  11. If you are restoring a Standard Edition server, browse to the Lync Server 2010 installation folder or media, and start the Lync Server Deployment Wizard located at \setup\amd64\Setup.exe. Use the Lync Server Deployment Wizard to do the following:

    1. Run Step 1: Install Local Configuration Store to install the local configuration files.

    2. Run Step 2: Setup or Remove Lync Server Components to install the Lync Server server roles.

    3. Run Step 3: Request, Install or Assign Certificates to assign the certificates.

    4. Run Step 4: Start Services to start services on the server.

    For details about running the Deployment Wizard, see the Deployment documentation for the server role you are restoring.

  12. Restore Location Information data to the Central Management store. At the command line, type:

    Import-CsLisConfiguration -FileName <LIS backup file name>

    For example:

    Import-CsLisConfiguration -FileName "D:\E911Config.zip"

  13. Restore user data by performing the following:

    1. Copy BackupUsers.xml from $Backup\ to a local directory.

    2. For Enterprise Edition, verify that at least one Front End Server in the pool is running and that the User Replicator process has completed a full synchronization cycle. The next procedure in this section describes how to verify that user replication is complete.

      Note

      The initial synchronization might take some time to complete. If you run Dbimpexp.exe before the synchronization is complete, the command will fail.

    3. To restore the user data, at the command line, type:

      Dbimpexp.exe /hrxmlfile:<path and file name of backed up Rtc database> /sqlserver:<SQL Server FQDN>\<instance name> /import /restype:all

      For example:

      Dbimpexp.exe /hrxmlfile:D\BackupUsers.xml /sqlserver:sql.contoso.com\rtc /import /restype:all

  14. If you deployed Response Group on this pool or Standard Edition server, restore the Response Group configuration data. For details, see Restoring Response Group Settings.

  15. If you are restoring a Back End Server that included Archiving or Monitoring databases, restore the Archiving or Monitoring data by using a SQL Server management tool, such as SQL Server Management Studio. For details, see Restoring Monitoring or Archiving Data.

To verify user replication has completed

  1. Log on to the computer as a member of the RTCUniversalServerAdmins group.

  2. Click the Start menu, and then click Run.

  3. Enter eventvwr.exe and then click OK.

  4. In Event Viewer, click Applications and Services logs to expand it, and then select Lync Server.

  5. In the Actions pane click Filter Current Log.

  6. From the Event sources list, click LS User Replicator.

  7. In <All Event IDs> enter 30024 and then click OK.

  8. In the filtered events list, on the General tab, look for an entry that states user replication has completed successfully.