You can edit various settings of the Data Insight servers from the
> > page.The advanced settings are divided into the following categories:
Filesystem Scanner settings - Configures how the server scans file systems. Data Insight performs two types of scans on the configured shares:
Full scans
During a full scan, Data Insight scans the complete share. These scans can run for several hours, if the share is very big. Typically, a full scan should be run once for a newly added share. After the first full scan, you can perform full scans less frequently based on your preference. Ordinarily, you need to run a full scan only to scan those paths which might have been modified while event monitoring was not running for any reason. In all other cases, the incremental scan is sufficient to keep information about the file system metadata up-to-date.
See Table: File system scanner settings - Full scan settings.
Incremental scans
During an incremental scan, Data Insight re-scans only those paths that have been modified since the last full scan. It does so by monitoring incoming access events to see which paths had a create event or write event on it since the last scan.
See Table: File system scanner settings - Incremental scan settings.
Indexer settings - Configures how the indexes are updated with new information. This setting is applicable only for Indexers.
Audit events preprocessor settings - Configures how often raw access events coming from file servers must be processed before they are sent to the Indexer.
High availability settings - Configures how this server is monitored.
Each server periodically monitors its CPU, memory, state of essential services, number of files in its inbox, outbox, and err folders. Events are published if these numbers cross the configured thresholds. Also, each worker node periodically heartbeats with the Management Server. The Management Server publishes events if it does not receive a heartbeat from a node in the configured interval.
FPolicy safeguard settings - Configures the safeguards related to FPolicy communication. You can either choose to use the global settings or customize the settings for a specific Collector node. You can configure settings for FPolicy Cluster-Mode and 7-mode
Report settings - Configures settings for reports.
Windows File Server Agent settings - Configures the behavior of the Windows File Server filter driver. This setting is applicable only for the Windows File Server Agent server.
Veritas File System server (VxFS) settings - Configures how Data Insight scans the VxFS filer.
NFS settings - Configures how Data Insight scans NFS shares.
See Table: NFS settings.
SharePoint settings - Configures the duration for which old audit logs are kept on the SharePoint server. Audit logs that are fetched from the SharePoint server are automatically deleted from the Data Insight database. You can disable this feature at the web application level.
Troubleshooting settings - Configures settings that aid troubleshooting.
Set custom properties - Configures certain advanced properties of a Data Insight worker node. Using this facility, you can customize certain properties that are not accessible by the normal settings.
You can configure the advanced settings per node or save commonly used settings as a templates. See About node templates.
To configure advanced settings
Each of the categories for the advanced settings are described in detail below.
Table: File system scanner settings - Full scan settings
Table: File system scanner settings - Incremental scan settings
Table: File system scanner settings - Throttling for NetApp filer
Table: File system scanner settings - Common settings
Table: Indexer settings
Table: Audit events preprocessor settings
Setting |
Description |
---|---|
Audit events preprocessor schedule |
Incoming raw audit events from file servers must be pre-processed before sending them to the Indexer. At this stage, By default, raw events are processed every 2 hours. |
Batch size (MB) |
The maximum size of the raw audit event files that a single Collector thread can process. The default batch size is 2 GB. |
Total Collector threads |
The Collector can run multiple pre-processors in parallel. This setting configures how many instances can run in parallel. |
Table: FPolicy safeguard settings
Setting |
Description |
---|---|
Use global settings |
This option is selected by default. Use the FPolicy safeguard settings for NetApp 7-mode and Cluster-mode filers as defined on the > > page.See Configuring scanning and event monitoring . Data Insight collects latency information from NetApp file servers. It can use this information to initiate safeguard mode, if latency of the file server increases above or falls below a certain level. When the safeguard is in effect, Data Insight drops its FPolicy connection to the filer. This ensures event collection does not put additional load on the file server in peak load conditions. If the latency on the physical file server increases above the configured threshold, Data Insight disconnects from the associated virtual file server. This information is also displayed on the Data Insight System Overview dashboard. |
Use custom settings |
Select to disable the safeguard settings or to override the global safeguard thresholds and define custom values. |
Enable FPolicy safeguard settings |
Select one of the following, as appropriate:
These FPolicy safeguard settings are not selected by default. When these check boxes are cleared, the safeguard settings are not in effect. Configure the following values:
|
Table: High availability settings
Setting |
Description |
---|---|
Ping timeout (in minutes) |
If a worker node does not heartbeat in the specified interval, Management server will publish an event to that effect. This setting is only applicable for the Management Server. |
Notify when CPU continuously over (percentage) |
If CPU used on this server is consistently over the specified percentage, an event is published. (Default value: 90%) |
Notify when memory continuously over (percentage) |
If Memory used on this server is consistently over the specified percentage, an event is published. (Default value: 80%) |
Notify when disk usage over (percentage) |
If disk usage, either for the system drive or data drive, is over the specified threshold, an event is published. (Default value: 80%) |
Notify when disk free size under (MB) |
If the free disk space for the system drive or data drive is over the specified threshold in megabytes, an event is published. (Default value: 500 MB) |
Notify when number of files in |
If Data Insight is not able to process an incoming file for some reason, that file is moved to an |
Notify when number of files in |
If Data Insight is not able to process incoming data fast enough, the number of files in the transient folders, |
Table: Reports settings
Setting |
Description |
---|---|
Maximum memory when generating report output |
Specifies the maximum memory that can be used for generating a report output. By default, it is 1024 MB on a 32 bit machine and 2048 MB on a 64 bit machine |
Total threads for generating report output |
Configure the number of threads for generating report output (PDF/HTML/CSV) in parallel. Default value is 2. This setting applies to the Management Server. |
Number of threads for a single report run |
Configure the number of threads responsible for generating the report output database for a single report. This configuration applies to the Indexer node. This setting helps you speed up the process of report generation. For a particular Data Insight server, the thread count applies to all types of reports. |
Maximum reports that can run simultaneously |
By default, Veritas Data Insight Administrator's Guide executes two reports in parallel. However, you can configure a higher value to run multiple reports in parallel. |
Table: Windows File Server agent settings
Setting |
Description |
||
---|---|---|---|
Maximum kernel ring buffer size |
The Windows File Server filter driver puts events in an in-memory buffer before the DataInsightWinnas service, consumes them. By default, it uses a 10MB buffer. You can use a bigger buffer. Data Insight publishes an event that indicates events are being dropped due to a high incoming rate.
|
||
Ignore accesses made by Local System account |
The Windows File Server filter driver ignores accesses made by processes running with Local System account. This setting ensures that Data Insight can ignore most events originating from the operating system processes or other services like antivirus and backup. Clear this check box to enable monitoring accesses made by LOCAL SYSTEM account. This is not recommended on a production file server. |
Table: Veritas File System server settings
Setting |
Description |
---|---|
Flush events on VxFS filer before audit |
Set this option to true, if you want to force VxFS to flush its events to disk each time Data Insight requests for information. This option is useful in Proof-of-Concept (POC) setups and enables you to see events faster. |
Maximum number of audit threads |
This option determines how many filers to fetch audit information from in parallel. |
Maximum kernel ring buffer size (Number of records) |
The access event records are saved in a log file on the VxFS filer before Data Insight consumes them. By default, 50,000 records can be saved in the log file. You can also specify a larger number. Data Insight publishes an event that indicates that events are being dropped due to a high incoming rate. |
Table: NFS settings
Setting |
Description |
---|---|
Set default credentials for NFS scanner |
Set this option to true if you want to allow Data Insight to use the specified User and Group ID to log in to scan NFS shares. |
User ID |
The ID of the NFS user that the Data Insight uses to scan the filer. You can set the value to 0 to allow root access from the Data Insight scan hosts. |
Group ID |
The ID of the group that the Data Insight uses to scan the filer. You can set the value to 0 to allow root access from the Data Insight scan hosts. |
Table: SharePoint settings
Setting |
Description |
---|---|
Automatically delete audit events from SharePoint server that are older than (days) |
When configuring a SharePoint web application, you can choose to let Data Insight delete audit logs that have already been fetched from SharePoint. By default, Data Insight deletes audit logs older than two days. Deletion of audit logs takes place every 12 hours. |
Schedule to fetch audit events from SharePoint server |
Data Insight fetches new audit events from SharePoint periodically. By default, it does so every 2 hours. You can configure a different schedule. |
Maximum scans to run in parallel on this server |
The Collector can perform multiple full scans in parallel. This setting puts a limit on the total number of full scans that can run in parallel on a Collector. The default value is two threads. Configure more threads, if you want scans to finish faster. The setting is disabled by default. |
Scan multiple site collections of a web application in parallel |
This setting indicates if the scanner can perform a scan on multiple site collections of the same web application in parallel. The setting disabled by default. |
Maximum site collections per web application to scan in parallel |
If multiple site collections of a web application can be scanned in parallel, this setting puts a limit on the total number of site collections of a web application that you can scan in parallel. |
Default scan schedule |
Specifies how often scans need to be performed. You can override this setting at a web application or site collection level. By default, scans are scheduled to repeat 11:00 P.M. each night. |
Pause scanner for specific times |
You can configure the hours of the day when scanning should not be allowed. This ensures that Data Insight does not scan during peak loads on the SharePoint servers. The setting is enabled by default. Scans resume from the point they were at before they were paused. |
Pause scanner schedule |
Specify when scanning should not be allowed to run. By default, scanning is paused from 7:00 A.M. to 7:00 P.M., Monday to Friday. |
Table: Troubleshooting settings
Setting |
Setting |
---|---|
Preserve intermediate files |
As new data comes into a Data Insight system, it moves between various modules. In this process the original files are deleted and a new processed file is generated for the next stage of processing. To aid troubleshooting, select this check box to retain the intermediate data files. These files get stored in |
Preserve raw audit event files |
Events processed by the Audit Pre-processor stage are deleted once consumed. If this setting is enabled, raw audit event files will be preserved in the |
More Information