Answer
GFI LanGuard’s backend database
GFI LanGuard's backend database (named as LNSSScanResultsXX, where the XX corresponds to the versions number) expects a minimum of 1 MB of data for a preset vulnerability scan, per machine. This can vary greatly depending on the number of installed and missing patches, applications, etc.
Configuring your data retention settings and SQL Server settings for the database can help avoid some of the following problems:
- slow user interface.
- agent scan takes a long time to begin.
- remediation fails to consistently complete.
- remediation pending completion for a long period of time.
GFI LanGuard - Data Retention Settings:
The data retention settings are locate under Configuration > Database Maintenance Options > Manage retention policy
GFI recommends the following:
- Scan results: 5 scans per target per profile or less.
- Scan history: 3 month or less.
Note: Scan history, as seen in the History tab or reports is a listing of differences between the most recent scan being imported and the last scan of the same type.
SQL Server Settings - LNSSScanResults database
- Exclude the data directory and the log directory from AV scanning.
- Put the database file and log files on different drives.
- Change the auto-growth settings to allow the database file and log file to expand.
- If using too much memory restrict it from using all the memory.
- Make sure SQL server has access to all processors.
- Check the size of the log file periodically and keep it small by implementing one of the following:
- Configure full backups on the database. This will shrink the log file to a few MB every time the backup runs
- Periodically run a shrink job on the database (or just the log file) Large transaction log can cause your queries to be very slow.
- Monitor the performance in Performance Monitor > Disk > Storage > Drives > Active time. High disk activity means bad performance.