[KB8598] How to reduce database size for ESET INSPECT On-Prem

Issue

  • Reduce disk space consumption for ESET Inspect On-Prem
  • Save disk space used by stored events

Solution

Storing less low-level data will not lower the protection because events are still being analyzed to detect suspicious activity.

Windows Server operating system partition capacity must not fall below 10 percent capacity

If the Windows Server operating system space falls below 10 percent of the partition capacity (C:\), ESET Inspect On-Prem stops accepting data from endpoints.

To reduce disk space usage, follow the steps below that are applicable to your system configuration. 

  1. Configure the length of time to store low-level data (for example, write a file, do a DNS lookup, or create a registry entry) in the More Settings Database Retention pane.   
    Store low-level data for the shortest possible time

    The database size is proportional to the amount of low-level data stored in the database, so lower the amount by keeping the low-level date as briefly as possible. For more information, see the Online Help topic Settings

  2. To configure the amount of low-level data is stored, change the amount in the More Settings Database collection pane. 
    Not all ESET Inspect On-Prem features will work or are limited when all data is not stored

    For more information about these limitations, see Data collection.

  3. Use Event Filters to selectively choose which low-level events to store from some executables or computers. Use Dashboard Events Load to find executables and computers that report most low-level events and where filters should be applied.

  4. Check your database settings that can cause increased disk usage:

    • MySQL: check binary log usage. For more information, visit the MqSQL documentation Binary Log

    • Microsoft SQL Server: Check recovery models. For more information, see the Microsoft documentation for Recovery Models (SQL Server)