dlp settings

Use this command to designate logical storage settings for the DLP fingerprinting database.

config dlp settings
    set storage-device {string}   Storage device name. size[35] - datasource(s): system.storage.name
    set size {integer}   Maximum total size of files within the storage (MB). range[16-4294967295]
    set db-mode {stop-adding | remove-modified-then-oldest | remove-oldest}   Behaviour when the maximum size is reached.
            stop-adding                  Stop adding entries.
            remove-modified-then-oldest  Remove modified chunks first, then oldest file entries.
            remove-oldest                Remove the oldest files first.
    set cache-mem-percent {integer}   Maximum percentage of available memory allocated to caching (1 - 15%). range[1-15]
    set chunk-size {integer}   Maximum fingerprint chunk size.  **Changing will flush the entire database**. range[100-100000]
end

Additional information

The following section is for those options that require additional explanation.

storage device <string>

Enter the storage device name, as configured under config system storage.

size <mb>

Enter the maximum total size of files in storage in MB. The default is set to 16.

db-mode {remove-modified-then-oldest | remove-oldest | stop-adding}

Select the method of maintaining the database size:

• remove-modified-then-oldest: Remove oldest chunks first, and then remove oldest files.
• remove-oldest: Remove oldest files first.
• stop-adding: Don't remove files and stop adding to database (set by default).

cache-mem-percent <percentage>

Enter the maximum percentage of available memory allocated to caching. Set the range between 1-15. The default is set to 2.

chunk-size <bytes>

Maximum fingerprint chunk size in bytes.

Changing the chunk size will flush the entire database. Document source fingerprints will repopulate with the next scan. Only manually updated fingerprints will be lost. Set the range between 100-100000 (or 100 bytes to 100 KB). The default is set to 2800. Smaller chunks allow for greater precision, but at the cost of increased processing, database size, and lookups. Note that changing this value will flush the database.