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 reenroll the certificates.

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

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

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.

Do one of the following:

• If you are installing a Standard Edition server, browse to the Lync Server installation folder or media, and then 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 2012 or SQL Server 2008 R2, keeping the instance names the same as before the failure.

  Note:
  Depending on the server that 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.

From a Front End Server, Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.

Re-create the Central Management store. At the command line, type:

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

For example:

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

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

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

For example:

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

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

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

	Copy Code
Import-CsConfiguration -FileName <CMS backup file name>

For example:

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

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

	Copy Code
Enable-CsTopology

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

If you are restoring an Enterprise Edition Back End Server that also hosted the CMS, or if you need to re-create a mirror of the CMS, then follow this step. Otherwise, skip to step 11.

Install the stand-alone databases by doing the following:

1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, 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 2013 node, and then click Install Database.

5. Follow the Install Database 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 Deployment Wizard.

6. If you are restoring a mirrored Back End Server, continue to follow the rest of the wizard until you come to a prompt of Create Mirror Database. Select the database you want to install, and complete the process.

7. 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, and the Install-CsMirrorDatabase cmdlet to configure mirroring. For details, see Install-CsDatabase and Install-CsMirrorDatabase.

If you are restoring a Standard Edition server, browse to the Lync Server 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 that you are restoring.

Restore user data by performing the following:

1. Copy ExportedUserData.zip from $Backup\ to a local directory.

2. Before you restore the user data, you must stop Lync services. To do so, type:

   	Copy Code
   Stop-CsWindowsService

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

   	Copy Code
   Import-CsUserData -PoolFqdn <Fqdn> -FileName <String>

   For example:

   	Copy Code
   Import-CsUserData -PoolFqdn "atl0cs-001.litwareinc.com" -FileName "C:\Logs\ExportedUserDatal.zip"

4. Restart Lync services by typing:

   	Copy Code
   Start-CsWindowsService

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

	Copy Code
Import-CsLisConfiguration -FileName <LIS backup file name>

For example:

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

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.

If you are restoring a Back End Server that includes 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.