Arctera Insight Information Governance Administrator's Guide
- Section I. Getting started
- Introduction to Arctera Insight Information Governance administration
- Configuring Information Governance global settings
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Information Governance integration with 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 Information Governance
- Configuring Information Governance product users
- Configuring Information Governance 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 Information Governance
- Configuring containers
- Server Pools
- Section III. Configuring native file systems in Information Governance
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Information Governance 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 Arctera File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring clustered NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Information Governance 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
- Configuring Azure Netapp Files Device
- Managing cloud sources
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Configuring policies
- Managing policies
- Configuring policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Information Governance best practices
- Appendix B. Migrating Information Governance components
- Appendix C. Backing up and restoring data
- Appendix D. Arctera Information Governance health checks
- About Information Governance health checks
- About Information Governance health checks
- Appendix E. Command File Reference
- Appendix F. Arctera Information Governance jobs
- Appendix G. 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 Information Governance 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 Information Governance 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.
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.