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
Resolving FPolicy connection issues
To resolve FPolicy connectivity issues perform the following checks:
Check the network connectivity. See if you can connect to the Collector from the filer using the short name or the Fully Qualified Host Name of the Collector and vice versa.
Ensure that host name or IP DNS lookup is working. The DNS lookup and reverse-lookup for host name of the Collector node from the filer should be working fine.
Verify that the system-time on the Collector and the filer are within 5 minutes of the time on the Domain Controller.
Check that the firewall settings or security software on the Collector are not blocking port numbers 139 and 445.
Verify that the user whose credentials are used to configure the DataInsightFPolicy service belongs to the same domain as the Data Insight Collector node and the NetApp filer. Ensure that this user is a part of the Backup Operators group on the filer.
If the NetApp filer and Data Insight Collector node are in different domains, ensure that the DataInsightFPolicy service is running as Local System or there is bidirectional trust between the domains to which the filer and the Collector belong.
Once you performed all the checks mentioned in the earlier procedure, you might need to perform the following additional checks if the problem persists:
Network Settings on the Collector: If you are using a supported version of a Windows machine as a Collector, verify the local security policy for the named pipes that can be accessed anonymously.
See “To verify the correct network security policy for FPolicy”.
Setting entry in the hosts file on the filer: The hosts file entry on the filer and the format of the hosts file entry. The entry should be in the format shown:
<IP_ADDRESS> <FQDN> <Short_name>
For example,
10.209.88.190 mycollector.tulip.matrixad.local mycollector
SMB signing check on the filer and the Collector: Disable the SMB signing on the filer and the Collector.
To verify the correct network security policy for FPolicy
- On the Collector node, navigate to the Control Panel.
- ClickSystem and Security > Administrative tools > Local Security Policy > Local Policies > Security options.
- Check if the value for the policy called "Network access: Named Pipes that can be accessed anonymously" is NTAPFPRQ.
- Restart the Collector node if you have made any changes.