Restoring Monitoring or Archiving Data
Topic Last Modified: 2011-05-16
Restoring monitoring and archiving data is not required to get Lync Server 2010 up and running after a failure. However, if monitoring and archiving data is critical to your organization, you will want to restore the data after you recreate the databases. If you are restoring a Monitoring Server or an Archiving Server with a collocated database, first perform the procedure for restoring the server roles. For details, see Restoring a Monitoring Server or Archiving Server with Collocated Database. If you are restoring a stand-alone Monitoring database or Archiving database, first perform the procedure for recreating the database. For details, see Restoring a Stand-alone Monitoring or Archiving Database. Then perform the following procedure to restore the data from the backup file.
The following procedure describes how to use SQL Server Management Studio to restore archving or monitoring data.
To restore monitoring or archiving data from a backup file
Log on to the server you are restoring as a member of the Administrators group on the local computer or a group with equivalent user rights.
Open SQL Server Management Studio: click Start, click All Programs, click Microsoft SQL Server 2008 R2, Microsoft SQL Server 2008, or Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In Connect to Server, connect to the SQL Server instance by providing at least the name of the server and the authentication information.
In Object Explorer, right-click Databases, and then click Restore Database.
Under Select a page, click General, and then in To database select the database name as follows:
For an Archiving database, select LcsLog.
For a call detail recording (CDR) database, select LcsCDR.
For a Quality of Experience (QoE) database, select QoEMetrics.
Click From device.
Under Select the backup sets to restore, click the backup file, and then click Restore.
Under Select a page, click Options, verify that the data file path and log path are in the correct folder, and then click OK.
To ensure that access control lists (ACLs) are correct
Expand Databases, expand the archiving or monitoring database, expand Security, and then expand Users.
Verify that the domain group RTCComponentUniversalServices exists as a user.
If the database is collocated with the Archiving Server or Monitoring Server, verify that the local group for the computer, RTC Component Local Group, also exists as a user.
If RTCComponentUniversalServices or RTC Component Local Group does not exist under Users, do the following:
Right-click Users, and then click New User.
In Login name, type the missing group name, RTCComponentUniversalServices or RTC Component Local Group.
Under Database role membership, select the ServerRole permission, and then click OK.
You do not need to restart the archiving or monitoring service.