Configuring Log Database maintenance options

Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.x

Related topics:

Log Database administration settings

Configuring database partition options

Configuring Internet browse time options

Configuring how URLs are logged

Configuring trend and application data retention

Use the Database Maintenance section of the Settings > Reporting > Log Database page to control when the database maintenance job runs, whether and how often database partitions are automatically deleted, and how often tasks like reindexing partitions and deleting error log messages occur.

For Maintenance start time, select the time of day for running the database maintenance job (01:00 hours, by default).

The time and system resources required by this job vary depending on the tasks you select in this area. To minimize any impact on other activities and systems, it is best to run this job during a slow time on the network, different from the time set for the IBT job (see Configuring Internet browse time options).

To permanently delete partitions based on age, select Automatically delete partitions when data is older than, and then specify the number of days (from 1 to 1825) after which to delete the partitions.


	Warning After a partition has been deleted, the data cannot be recovered. See Configuring database partition options for an alternative way to delete partitions.

Select Enable automatic reindexing of partitions, and then select a day of the week to have this processing performed automatically each week (Saturday, by default).

Reindexing the database is important to maintain database integrity and to optimize reporting speed.


	Important It is best to perform this processing during a quiet time on the network. Reindexing database partitions is resource intensive and time-consuming. Reports should not be run during the process.

Select Process failed batches during the database maintenance job to have the nightly database maintenance job reprocess any failed batches.

Failed batches occur when there is insufficient disk space or inadequate database permissions to insert log records into the database. Typically, these batches are successfully reprocessed and inserted into the database during the nightly database maintenance job. Reprocessing, however, cannot be successful if the disk space or permission problem has not been resolved.

If this option is unchecked, failed batches are never reprocessed. Instead, they are deleted after the time specified (below), if any.

Select Delete failed batches after and then enter a number of days (from 0 to 90; 20, by default) after which to delete any failed batches.

If this option is not selected, failed batches are retained indefinitely for future processing.

Select Delete the error log after, and then enter a number of days (0 to 90; 60, by default) after which to delete database error records from the catalog database.

If this option is not checked, error logs are retained indefinitely.

Click OK to cache your changes. Changes are not implemented until you click Save and Deploy.


	Note Advanced file analysis data is maintained for 120 days.The database maintenance job purges data that is older than 120 days.