Topic Last Modified: 2011-05-13

If an Enterprise Edition Back End Server fails, follow the procedures in this section. If the Central Management store fails, see Restoring the Central Management Store. If an Enterprise Edition member server that is not the Back End Server fails, see Restoring an Enterprise Edition Member Server.

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 an Enterprise Edition Back End Server

  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.

    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. Install SQL Server 2008 R2, SQL Server 2008, or SQL Server 2005, keeping the instance names the same as before the failure.

    Depending on your deployment, the Back End 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.
  4. After you install SQL Server, perform 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. On the Create databases page, select the databases you want to recreate.

      Only stand-alone databases are displayed on the Create databases page.
    6. Follow the rest of the wizard, and then click Finish.

    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.
  5. Restore user data by performing the following:

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

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

    3. 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. For details about how to verify that user replication is complete, see Verify User Replication has Completed in the Migration documentation.

      The initial synchronization might take some time to complete. If you run Dbimpexp.exe before the synchronization is complete, the command will fail.
    4. To restore the user data, at the command line, type:

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

      Copy Code
      Dbimpexp.exe /hrxmlfile:D\BackupUsers.xml /\rtc /import /restype:all
  6. If you deployed Response Group on this pool, restore the Response Group configuration data. For details, see Restoring Response Group Settings.

  7. 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 tool, such as SQL Server Management Studio. For details, see Restoring Monitoring or Archiving Data.