Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- 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 user risk score
- About bulk assignment of custodians
- Configuring Metadata Framework
- 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
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp 7-mode 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 7-mode 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 site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Configuring monitoring of Box accounts
- Configuring OneDrive account monitoring
- Managing cloud sources
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Data Insight best practices
- Appendix B. Migrating Data Insight components
- Appendix C. Backing up and restoring data
- Appendix D. Data Insight health checks
- About Data Insight health checks
- About Data Insight health checks
- Appendix E. Command File Reference
- Appendix F. Data Insight jobs
- Appendix G. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Monitoring Indexer Node Storage Utilization
It has been observed that indexes get corrupt due to a lack of disk space on the Indexer nodes. Till this release, Data Insight was not able to stop indexing when the storage was low. To resolve this issue, Data Insight has introduced Disk Utilization Safeguard Levels. You can view Status of the indexer in the events log. Indexing status can also be tracked from Indexing Paused for Shares Stats in the Health audit Report.
See About the Health Audit report.
Refer to the next table for more details:
Status | Disk Utilization | Actions |
---|---|---|
HEALTHY | >65% | No action required |
WARN | >= 65% and below 75% | Initiate warning and send event notification for low storage. |
SEVERE | >=75% and below 90% | Pause the current index writer job for the given MSU. Send an event notification indicating that the index writer has been paused due to disk utilization exceeding 75% for a given share. |
CRITICAL | >= 90% | Pause all index writers for all MSUs. Send an event notification indicating that the index writer has been paused at the indexer node level due to disk utilization exceeding 85%. |
IndexWriterJob_cleanup and IndexWriterJob_autoResume will run every 15 and 5 minutes respectively on the indexer node to reclaim the used disk space and to resume indexing.
Note:
Latest data will not be available in the workspace and reports since indexing is throttled for given Share and Indexer node.