Overview
When scans come back with the same vulnerabilities even after the remediation was performed, this can happen when the database is full and does not update with new information and scan results.
This article provides information on setting up Database retention options to keep the database space in check and the new data ingestion consistent by configuring LanGuard to automatically delete unwanted scan results and scan history information while retaining important ones.
Solution
When the SQL Express reaches its database size limit or runs out of disk space, the LanGuard back-end database stops updating. This, in turn, means that it isn't importing new scan results or configuration changes, which leads to unexpected errors and inconsistent information in the LanGuard console.
One way to avoid this is by setting up the automated removal of old scans results through scheduled database maintenance. During scheduled database maintenance, LanGuard automatically deletes saved scan results based on the configured retention policies. To set this up:
- Launch GFI LanGuard console.
- Go to Configuration tab > Database Maintenance Options > Manage Retention Policy.
- Configure the options described below:
Option Description Keep scans generated during the last... Keep scan results generated during the specified number of days, weeks, or months. Keep scans per scan target per profile number of... Specify the number of scan results to keep for every scan target by every scan profile. Never delete history Select this option if you want to keep all scan history. Keep history for the last... Keep scan history for the specified number of days, weeks, or months.
- Click OK to apply the settings.
If the retention settings are greyed out, it means that LanGuard is currently performing a scanning operation. Check again once it is completed.