Use the procedures in this section to change the maximum number of days of instant messaging (IM) archiving data that the Archiving Server is to keep or the default time of day that the database purge occurs. It is recommended that the maximum days logged be at least 7 days and that record purging be scheduled during off-peak hours, when fewer instant messages and conferences are in progress.

Configuring Purging for Archiving Servers Connected to a Single Archiving Database

If you deployed an Enterprise pool in which multiple Archiving Servers are installed on separate computers and are connected to a single Archiving database, it is important to configure the purge start time on each Archiving Server so that the purges do not occur simultaneously. If multiple Archiving services attempt to purge at the same time, a database lock might occur. The database lock might resolve without intervention, but the event appears in the Event Viewer.

You can configure the purges in either of the following ways:

  • Set one Archiving Server to purge and the others to not purge.

    If you choose this method to control purging, you need to reconfigure the servers to continue purging in a failover situation.
  • Set the purge times sufficiently far apart so that the purges do not overlap.

For either of these methods, set Windows Management Instrumentation (WMI) settings as described in this topic. For details about changing WMI settings, see your Windows Server documentation.

If you choose to configure only one Archiving Server to purge, use WMI settings to set the number of retention days. For the Archiving Servers for which you want to suppress purging, set MSFT_SIPArchivingServiceSetting.DaysOfArchivingto zero (0). Set this WMI setting to a number from 1 to 2562 for the Archiving Server for which you want to purge data.

If you choose to control purging by setting the purge times, use WMI settings to set the purge time and ensure that the purges occur far enough apart so that they do not overlap. Use the following example to extrapolate the time you need to allow for purging in your organization. This example assumes 100,000 users per pool and eight working hours per day: A growth rate of 900M bytes per hour takes 70 minutes to purge a single day's data. It is recommended that you set the purge times at least an hour apart.

Configuring Purge Settings for Archiving Data

The following procedures describe how to set the number of days Archiving data is retained and the time of day that data is purged. The default time for purging Archiving data is 4:00 A.M. but you can change this setting as described in this topic.

To configure the maximum days to be retained

  1. Using an account that is a member of the RTCUniversalServerAdminsgroup, open the Office Communications Server 2007 R2 snap-in: Click Start, point to Administrative Tools, and then click Office Communications Server 2007 R2.

  2. In the console tree, expand the forest node, expand Archiving Servers, right-click the Archiving Server name, and then click Properties.

  3. Select the Archiving days loggedcheck box, and then, in the corresponding box, type the number of days to be logged.

    Valid values are from zero (0) to 2562. Records that are older than the specified maximum are automatically deleted, except that a value of zero (0) causes data to not be purged.
  4. If you changed the Archiving days loggedsetting, note that the change will take a few minutes to take effect.

To specify purge time

  • In WMI, change the PurgeTimeproperty in the MSFT_SIPArchivingServiceSettingclass.