18.3 Purging the Delete Log Database
This section describes how to purge the delete log database. Calendar Server provides two types of purging of the delete log database, automatic and manual.
This section contains the following topics:
18.3.1 Tuning Delete Log Purging
Before purging the delete log database, you need to be very aware of the end users you are serving. If your end users are using Communications Express, the default parameter settings should be adequate. If , however, they are using client user interfaces that store a local copy of the events and tasks, such as the Connector for Microsoft Outlook, or the Sync Tool, then you must adjust the settings of the automatic purge configuration parameters to fit their needs. Typically, they need the delete log to include up to 30 days or more of entries. This will cause the size of the delete log to increase dramatically. A failure to make this adjustment could cause problems with the database. The purge interval should also be adjusted to fit the needs of the users. For instance, there might not be a point in running purge every minute when your Delete log database is holding 30 days of data before it will be allowed to be purged. Things will age out daily, though, so a daily purge would be reasonable.
Similar problems can occur running cspurge manually. If too much is removed from the Delete log, it can cause users of the Connector for Microsoft Outlook and the Sync Tool to get out of sync with the server database.
Waiting too long to purge the Delete log database can cause the files to grow very large. Then, when a giant purge occurs, daily transaction logs grow greatly, reflecting the fact that each item purged is a transaction recorded in those logs and then archived to the archive and hot backups. These large anomalies in the transaction logs can make it appear as if there is a system problem and cause time to be lost figuring out what happened.
18.3.2 Automatic Purge of the Delete Log Database
If you wish, you can have Calendar Server automatically purge entries in the Delete Log database at a specified interval. By default the automatic purge is disabled.
The following ics.confparameter controls the automatic purge feature.
Table 18–1 Configuration Parameters for Automatic Purge of the Delete Log Database|
Parameter |
Description |
|---|---|
|
Enables ("yes") or disables ("no") the automatic purge of Delete Log database (ics50deletelog.db) entries. The default is "no". |
|
|
Specifies the interval time in seconds to automatically purge entries in the Delete Log database (ics50deletelog.db). The default is 60 seconds. |
|
|
Specifies a time in seconds before which to purge entries in the Delete Log database (ics50deletelog.db). The default is 518400 seconds (6 days). |
For example, to have Calendar Server automatically purge Delete Log database entries every five minutes (600 seconds) that are more than 2 days old (172800 seconds), set parameters in 18.3.2 Automatic Purge of the Delete Log Database as follows:
service.admin.purge.deletelog="yes" caldb.berkeleydb.purge.deletelog.interval=600 caldb.berkeleydb.purge.deletelog.beforetime=172800
After you set these parameters, restart Calendar Server for the new values to take effect.
18.3.3 Manual Purge of the Delete Log Database
You can choose to manually purge entries in the Delete Log database (ics50deletelog.db), using the cspurge utility:
Usage of this utility is as follows:
cspurge -e endtime -s starttime
The variables endtime and starttime specify the ending and starting times in Zulu time (also referred to as GMT or UTC).
To run cspurge, you must be logged in as the user and group under which Calendar Server is running (defaults are icsuser and icsgroup) or as root.
For example, to purge entries from July 1, 2003 through July 31, 2003:
cspurge -e 20030731T235959Z -s 20030701T120000Z
For more information, see D.13 cspurge.
- © 2010, Oracle Corporation and/or its affiliates