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
Credentials required for configuring a clustered NetApp file server
Table: Credentials for configuring NetApp file servers in Cluster-Mode
Credential | Details |
---|---|
Credentials required during filer configuration through the Data Insight Management Console. Data Insight uses these credentials to discover shares and enable FPolicy on the NetApp Cluster-Mode filer. | This credential belongs to the NetApp ONTAP cluster administrator user who is a local user on the ONTAP cluster. Or, this credential belongs to the ONTAP cluster non-administrator user with specific privileges. See Preparing a non-administrator local user on the clustered NetApp filer . |
Credentials required for scanning of shares. | Required for scanning of shares from the NetApp filer. When scanning CIFS shares, this credential belongs to the user in the domain of which the NetApp filer is a part. This user must belong to either the Power Users or Administrator's group on the NetApp filer. If the credential is not part of one of these groups, the scanner is not able to get share-level ACLs for shares/exports of this filer. Run the following commands on every Storage Virtual Machine (SVM) that Data Insight is monitoring: cifs users-and-groups local-group add-members -vserver <vserver name > BUILTIN\Administrators -member-names <domain name \usename> cifs users-and-groups local-group add-members -vserver <vserver name > BUILTIN\Power Users -member-names <domain name \usename> You do not need this privilege if you do not want to get the share-level ACLs. In this case you only need privileges to mount the share and scan the file system hierarchy. You must have the share-level READ permission. Additionally, the folder within the share must have the following file system ACLs:
|