Backup and Restoration Worksheets

http://technet.microsoft.com/en-us/library/hh202169.aspx

Pool and server backup

The backup and restoration plan should include all information required to complete backup procedures on an ongoing basis. The primary information to be communicated to responsible team members includes the following:

Team or person (specified as an individual or role) responsible for backing up each server Specific schedules for backing up each server Backup locations for each type of data (settings, database, and file shares) Backup procedures to be used, including the tools required to complete each procedure Information required to complete backups, as covered in Backup and Restoration

Worksheets. Validation methods to be used to ensure that data and settings are appropriately backed up

and available for restoration, which can include periodic audits and test restorations.

Restoration of service

The backup and restoration plan should include all information required to restore service, in case one or more servers suffers a loss that makes service unavailable. The primary information to be communicated to responsible team members includes the following:

Team or person (specified as an individual or a role) that is responsible for determining when restoration of service is required and the procedures to be used to restore service, and also the team or person responsible for implementing procedures for each restoration scenario.

Criteria for determining which restoration procedures are most appropriate for a specific situation.

Time estimates for restoration of service in each restoration scenario. Restoration procedures to be used, including the tools required to complete each

procedure. Information required to restore data and settings. Worksheets are provided in Backup and

Restoration Worksheets.

Validating Backup and Restoration Operations

After completing initial backup efforts in your production environment and at specified intervals (as covered in your backup and restoration plan), you should verify the following:

Backups are occurring as required. Backed up data and settings are accessible. Restoration procedures can be performed within the times specified in the backup and

restoration plan and the results meet all business requirements, as specified in your backup and restoration plan.

Backup worksheets have been completed and verified, and they are stored in a secure location. These worksheets are provided in Backup and Restoration Worksheets.

Restoration procedures have been tested and verified to work as expected, as specified in your backup and restoration plan.

http://blogs.technet.com/b/nexthop/archive/2011/09/29/microsoft-lync-server-2010-standard-edition-disaster-recovery-plan-part-1.aspx

A disaster recovery plan should include the following: a replacement hardware server, a current backup of the existing Lync Server 2010 Standard Edition topology components, and backups of the Lync Server 2010 Standard Edition user information

You need to back up the following types of information: •Local Central Management store

•Topology information

•User contacts and meeting information

•Lync Server 2010 file store information

Back Up the Local Central Management Store

To back up the Lync Server 2010 Standard Edition configuration, you must have a consistent plan for preserving the local Central Management store information. You can manage this by performing the following procedure at the required intervals:

1. From a user account that is a member of the RTCUniversalServerAdmins group, log on to the Microsoft Lync Server 2010 Standard Edition, Front End Server.

2. To store the backup files, create a network share with the correct permissions on a different server or removable drive.

3. On the Start menu, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

4. Back up the Central Management store configuration file by typing the following at the command prompt:

Export-CsConfiguration -FileName \\server01\remoteshare\currentCMSbackup.zip

Export-CsConfiguration -FileName "F:\CMSbackup.zip"

Back Up Topology Information

You should back up the Lync Server 2010 Standard Edition topology after any updates to the Lync Server 2010 infrastructure have been published to the Lync Server 2010 Standard Edition Central Management store. To do this, use the Lync Server Topology Builder as follows:

1. On the Start menu, click All Programs, click Lync Server 2010, and then click Lync Server Topology Builder.

2. In the Topology Builder dialog box, click Download topology from the existing deployment, and then click OK.

3. In the Save Topology As dialog box, save the latest copy of the Topology Builder file to a removable device or a shared folder on a remote file server.

Back Up User Contacts and Meeting Information

Lync Server 2010 user contacts and meeting information is stored locally in the local instance of the RTC database (local)\RTC. You can back up and restore this information as part of the prescribed disaster process by using the Lync Server 2010 Database Import Export utility (Dbimpexp.exe). The Dbimpexp.exe tool is located in the installation support folder for Lync Server 2010 located at <drive:>\<Lync Server 2010 Installation Folder>\Support.

The following steps describe how to use the Dbimpexp.exe tool locally on the Lync Server 2010 Front End Server:

1. At a command prompt, run the following command to create an XML backup file that contains the Lync Server 2010 users’ contacts and meeting information using the Lync Server 2010 Dbimpexp.exe tool:

Dbimpexp.exe /hrxmlfile:”c:\BackupUser.xml”

2. Copy the BackupUser.xml file to a network share on different server or removable drive

http://technet.microsoft.com/en-us/library/hh202159.aspx

In Lync Server 2010, much of the settings and configuration data that were previously stored in Active Directory Domain Services (AD DS) and the settings and configuration data that were stored on individual servers are now stored in the Central Management store. Global-level, site-level, pool-level, and server-level settings and configuration data are backed up and restored when you back up and restore the Central Management store.

http://technet.microsoft.com/en-us/library/hh202194.aspx

Backup and Restoration Requirements: Data

Settings and Configuration Requirements

This document includes procedures for backing up and restoring the settings and configuration information that is required for recovery of Lync Server service. This information is located in the Central Management store or on another back-end database or Standard Edition server.

The following table identifies the settings and configuration information you need to back up and restore.

Settings and Configuration DataType of data Where stored Description / When to back up

Topology configuration information

Central Management store (database: Xds.mdf)

Topology, policy, and configuration settings.

Back up with your regular backups and after you use Lync Server 2010 Control Panel or cmdlets to modify your configuration or policies.

Location information

Central Management store (database: Lis.mdf)

Enterprise Voice Enhanced 9-1-1 (E9-1-1) configuration information. This information is generally static.

Back up with your regular backups.

Response Group configuration information

Back End Server or Standard Edition server (database: RgsConfig.mdf)

Response Group agent groups, queues, and workflows.

Back up with your regular backups and after you add or change agent groups, queues, or workflows.

Data Requirements

This document includes procedures for backing up and restoring only the data that is required to recover Lync Server service.

The following table identifies the data you need to back up and restore.

Data Stored in DatabasesType of data Where stored Description / When to back up

Persistent user data

Back End Server or Standard Edition server (database: Rtc.mdf)

User rights, user Contacts lists, server or pool data, scheduled conferences, and so on.

Note:

This user data does not include content uploaded to a conference.

Back up with your regular backups. This information is dynamic, but the loss of updates is not catastrophic to Lync Server if you need to restore to your last regular backup. If Contacts lists

are critical to your organization, you can back up this data more frequently.

Archiving data

Archiving database (database: LcsLog.mdf)

May be collocated on an Archiving Server, Back End Server, or other server, or may be on a stand-alone server

Instant messaging (IM) and meeting content.

This data is not critical to Lync Server, but it may be critical to your organization for regulatory purposes. Determine your back up schedule accordingly.

Lync Server 2010 supports only the Simple Recovery model for Archiving databases. With the Simple Recovery model, databases are recovered to the point of last full backup, which means that you cannot restore a database to the point of failure or to a specific point in time.

Monitoring data

Monitoring databases (LcsCDR.mdf and QoeMetrics.mdf)

May be collocated on a Monitoring Server, Back End Server, or other server, or may be on a stand-alone server

Call detail records (LcsCDR.mdf) and Quality of Experience metrics (QoeMetrics.mdf).

Call detail records are dynamic and may be critical to your business. Determine your back up schedule by considering whether you need these records for regulatory reasons.

Quality of experience information is dynamic. Loss of QoE data is not critical for the operation of Lync Server, but it may be critical to your business. Determine your back up schedule based on how critical this information is to your organization.

Lync Server 2010 supports only the Simple Recovery model for Monitoring databases. With the Simple Recovery model, databases are recovered to the point of last full backup, which means that you cannot restore a database to the point of failure or to a specific point in time.

File Store Data Requirements

This document includes procedures for backing up data in file stores. In an Enterprise Edition deployment, the Lync Server file store is typically located on a file server. In a Standard Edition deployment, the Lync Server file store is located by default on the Standard Edition server. Typically, there is one Lync Server file store that is shared for a site. The Archiving file store may use the same file share as the Lync Server file store, or it may be in a separate file share.

File store locations are identified as \\server\share name. To find the specific locations of your file stores, open Topology Builder and look in the File stores node.

The following table identifies the file stores you need to back up and restore.

File StoresType of data Where stored Description / when to back up

Lync Server file store

Typically on a file server, file cluster, or a Standard Edition server

Meeting content; meeting content metadata; meeting compliance logs; application data files; update files for device updates; audio files for Response Group, Call Park, and Announcement applications.

Back up with your regular backups.

Archiving file store

Typically on a file store shared for a site, but may be separate

Copies of web conferencing (meeting) content.

Archiving data is critical for compliance purposes. Determine your back up schedule accordingly.

Additional Backup Requirements

Lync Server uses or depends on some data and components that you need to back up separately from the procedures in this document. The following components are not backed up or restored as part of the Lync Server backup and restoration process described in this document:

Active Directory Domain Services (AD DS) You need to back up AD DS by using Active Directory tools at the same time that you back up Lync Server. Although many Lync Server settings are now stored in Central Management store instead of in AD DS as in previous versions, AD DS still stores the following:

o User SIP Uniform Resource Identifier (URI) and other user settingso Contact objects for applications such as Response Group and Conferencing

Attendanto A pointer to the Central Management storeo Kerberos Authentication Account (an optional computer object) and Lync Server

security groups

Important:

It is important to keep the contact objects in AD DS synchronized with Lync Server to avoid problems that can occur when Lync Server expects contact objects that do not match those in AD DS.

For details about backing up and restoring AD DS in Windows Server 2008, see "AD DS Backup and Recovery Step-by-Step Guide" at http://go.microsoft.com/fwlink/?LinkId=209105. For details about backing up and restoring AD DS in Windows Server 2003, see "Administering Active Directory Backup and Restore" at http://go.microsoft.com/fwlink/?LinkId=209106.

Certification authority and certificates Use your organization's policy for backing up your certification authority (CA) and certificates. If you use exportable private keys, you can back up the certificate and the private key, and then export them if you use the procedures in this document to restore Lync Server. If you use an internal CA, you can re-enroll if you need to restore Lync Server. It is important that you retain the private key in a secure location where it will be available if a computer fails.

Public switched telephone network (PSTN) gateway configuration If you use Enterprise Voice or Survivable Branch Appliances, you need to back up the PSTN gateway configuration. See your vendor for details about backing up and restoring PSTN gateway configurations.

Microsoft Exchange and Exchange Unified Messaging (UM) Back up and restore Microsoft Exchange and Exchange UM as described in the Microsoft Exchange documentation. For details about backing up and restoring Exchange Server 2010, see http://go.microsoft.com/fwlink/?LinkId=209179. For details about backing up and restoring Exchange Server 2007, see http://go.microsoft.com/fwlink/?LinkId=209180.

Infrastructure information Back up information about your infrastructure, such as your firewall configuration, load balancing configuration, Internet Information Services (IIS) configuration, Domain Name System (DNS) records and IP addresses, and Dynamic Host Configuraton Protocol (DHCP) configuration. For details about backing up these components, check with their respective vendors.