The size of the database can be affected by several things you may have configured. For example, if you have old results that you have not purged, that will add to the size of the database. Also, if you are sending up "Preview Data" with your results, that will make the database twice as large, on average. Here are some recomendations to manage and reduce the overall size of your Spirion database:
The Purge Results Service Task is responsible for deleting results data. If you want the ability to purge empty searches without also purging search results, run the Purge Searches Service Task.
As endpoints send their search results up to the console, they are stored in the database but storing a large amount of results in the console database can take up a lot of space if they are allowed to accumulate over time, and this in turn may slow the performance of the console. If you find that you have a lot of search results stored in the console database that you no longer need, you can run the Purge Results service task to free up space and improve performance.
If you are just concerned with if a location has any matches in it then you may want to configure the endpoint to stop searching a location after it has found a match in it. You can do this by configuring the following settings in Policy:
Settings\Performance\MaximumMatches set to 2 or whatever value you wish.
To enable stopping search for a location and skipping to next location when MaximumMatches is reached, set this value to Enable (1).
Note: This setting will only take effect if the Performance\UseMultipleCores setting equals zero (Use only a single CPU core). By default, the search will use all available CPU cores when searching for AnyFind and OnlyFind information within a location.
The valid values are:
- 0: Use only a single CPU core
- 1 (Default): Use all available cores
- >1: Use a maximum of this many processor cores. For example, on a system with 8 cores, set this value to 4 to limit the search to a maximum of 4 cores.
Purge Match Previews
The Purge Match Previews service task is responsible for deleting the preview data from the console. The preview data is what is shown in the Location Preview section of the Results Details window. As endpoints send their preview data to the console, that data is stored in the console database. Storing large amounts of preview data can over time can consume a large quantity of database storage space which can in turn slow the performance of the console. When preview information is no longer necessary, you can run the Purge Match Previews service task to free up space and improve performance.
Endpoints can be configured to not send Match Preview Data by configuring the following setting in Policy:
Console\previewLength set to 0
To provide context to matches when viewing results on the console, version 7.0 and later of the endpoints and console can send the specified number of characters from before and after the match itself. By default, the 20 characters preceding and following the match will be sent to the console. The maximum allowed number of characters is 1000 and a value of 0 will disable sending preview information to the console.Valid values:
- 0: Disabled (no preview data will be sent to the console)
- 1-1000: The specified number of characters from before and after the match will be sent to the console
- >1000: Invalid (the value will be set back to the default of 20)
The Purge Logs Service Task is responsible for deleting log data.
Endpoints can be configured to send logs to the console, but storing a large amount of logs in the console database can take up a lot of space if they are allowed to accumulate over time, and this in turn may slow the performance of the console. If you find that you have a lot of unnecessary logs stored in the console database you can run the Purge Logs service task to free up space and improve performance.
Endpoints can be configured to not send search logs by configuring the following setting in Policy:
Console\sendLogs set to disabled (0) or reset the setting as it is disabled by default.
The Prune Endpoints Service Task is responsible for removing endpoints from the console. This Service Task is useful if you created an Active Directory tag with many computers that you do not want to view in the Console, or if there are old or decommissioned endpoints.
You may want to create a Prune Endpoints Service Task to remove endpoints that have not polled in a specified amount of time to remove endpoints from the Console that are no longer active.
Trace Log Cleanup
The Trace Log Cleanup service task will remove console and services logs based on a user specified time period. These logs can be viewed using the Console Administrator Tool (CAT). If the Console encounters an unexpected issue, a message will be written to a log file. Storing large amount of logs in the console database may slow the performance of the console over time. To delete old, unnecessary logs stored in the console database, you can run the Trace Log Cleanup service task.
Also ensure that you do not have additional logging enabled in the CAT: