Because Policy and Distribution Services logs all successes and failures for the Server Policies or Tiered Electronic Distribution components, zfslog.db can quickly grow in size. Therefore, you should periodically purge this database file.
The following database information types are purged using different methods:
To manually purge a selected database of all Tiered Electronic Distribution information older than a specific date and time:
In ConsoleOne, right-click the database object, then click .
In the Purge Database dialog box, select a date and time, then click .
Records older than the date entered are purged from the database.
When the purge has been completed, a dialog box is displayed indicating that the purge was successful.
Purging of policy information is done automatically according to how you configure the ZENworks Server Management policy and which of the following events occurs:
A server is restarted where the Policy/Package Agent is running that writes policy information to the database.
Server Management is restarted on a server where the Policy/Package Agent is running that writes policy information to the database.
On a server where The Policy/Package Agent is running that writes policy information to the database, the Policy/Package Agent is manually refreshed by typing the REFRESH command on the ZENworks Server Management console prompt.
The REFRESH command or Refresh option only causes database purging if given on a server where the database file resides.
In each of these events, the database file that is purged is the one written to by the associated Policy/Package Agent.
To set up policy information purging:
In ConsoleOne, do one of the following:
If you want to use a different policy package schedule for purging information than an existing Distributed Server Package (see Step 5) is using, in ConsoleOne click > > , select , and provide a name that identifies its purpose. For example, Purge_Policy_server_name, where server_name is the server where the zfslog.db file resides.
To use the same policy package that has other policies enabled, in ConsoleOne right-click the existing Distributed Server Package, then click .
In this case, we recommend that in Step 5 you select for the package schedule. That way, any change you make to the number of days in Step 3 is immediately available the next time a purge is triggered.
In the Distributed Server Package, select the check box, then click .
Select the tab and select a number of days.
The default is 100 days. Records older than the number of days that you determine are purged.
Select a number that maintains the desired database file’s size. The amount of policy-related information accrued in the database is determined by how often you have policies being run by servers writing to this database. Depending on how frequently you purge the database, you may need to experiment over time to determine the optimum number of days.
Click to close the policy’s properties.
To set the package schedule, do one of the following:
To accept the default package schedule, which is Run Event: System Startup, click to close the package’s properties.
To change the default schedule, click Edit, select a schedule, then click twice to close the package’s properties.
For more information on the schedules, see Section 4.7, Scheduling Policies.
The package schedule determines when any configuration changes that you make are available. For example, if you previously selected Event: System Startup for the package schedule and then later changed the 100 days to 60, that change is not recognized if the Policy/Package Agent is refreshed to trigger purging. It is only recognized after system startup occurs.
Create a Policy Package Distribution for this policy.
For more information, see Creating and Configuring the Distribution.
Send the Distribution to the Subscriber server where the zfslog.db file resides.
For more information, see Section 1.2.6, Sending the Distributions.
If this policy package is dedicated the ZENworks Server Management policy for purging, you need to send this Distribution only to each server where a database file resides, because you need just one instance of this policy per database file.