Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Generic checks
Generic checks for all servers include checks for the following information:
Configuration version
Component version
Resource usage statistics
Windbg
checkError files count
Error events check
Attic check
Crash dump check
Table: Configuration version checks lists three configuration scenarios that you must review, and their related steps:
Table: Configuration version checks
Configuration versioning | Steps |
---|---|
Are the versions on the Management Server and the other nodes consistent for configuration, users, and database? Note that the policy versions may vary. | Run the following command on Management Server/node: # configdb -V |
Are the versions on the Management Server lower than other Data Insight nodes? This behavior occurs in restore cases. | Contact Veritas Support for more information. |
Are the versions considerably higher on Management Server than the other Data Insight nodes? |
|
Perform one of the following steps to gather component versions for all nodes:
Navigate to
> .Or, to get the node number-wise breakdown of component versions, run the following command:
# configdb -p -T objattr_node| findstrnode_info_product.version
Note:
Data Insight Management Server, Indexer nodes, and Collector nodes must run the same version of Data Insight. Windows File Server agent version may be different from the Data Insight version on the head servers. Also note that Data Insight 5.0 supports Windows File Server agents later than version 4.0 or later.
To view the resource consumption statistics per server, on the Management Console, navigate to
> > .Verify that the average resource consumption is consistently high.
Table: Performance checks describes the various parameters you must verify in the Data Insight performance chart and the remedial steps required.
Table: Performance checks
Performance parameter | Steps |
---|---|
CPU usage is consistently high. | Look for processes clogging the server. |
CPU usage is consistently low. | Look for cores and threads settings in server-specific checks. Verify if a server is unable to process more load. |
Memory consumption is consistently high. | Look for processes clogging the server. |
Spike patterns exist in hourly or weekly charts, or both. | If the spikes occur in a weekly chart or hourly chart form a pattern, verify if they coincide with the Data Insight schedule. Also investigate other schedules on the servers. |
Figure: Disk usage chart illustrates a stable disk usage pattern.
The following table describes the remedial steps that you must perform, if disk usage increases to high levels.
Table: Disk usage checks
Disk usage | Steps |
---|---|
Disk usage is consistently high; that is, consistently reaching 100 per cent. |
OR
|
If the windbg
utility is installed, check for any processes that are captured and are running in windbg. For example, if you run a report that fails, say report.exe
, Windbg captures the process. Investigate if any process appears to be running, but is not functional.
To view the error file count, navigate to
> >Ideally, there should be no error files. View errors at the following location: datadir\indexer\err folder
.
Where datadir is the path of the data
directory
For example: C:\DataInsight\data\indexer\err
folder.
To verify if any error events are logged, navigate to:
> > .
Ensure that the attic feature is turned off on all Data Insight nodes.
That is, ensure that there are no intermediate files in the following directory: DATADIR/attic
.
Ensure there are no dump files in the following directory: INSTALLDIR/dumps
.