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
Enabling export of NFS shares on a NetApp Cluster-Mode file server
Before you add a NetApp Cluster-Mode file server to Information Governance, you must identify the volumes and export policies to allow Information Governance to discover the NFS shares on the cluster.
Information Governance requires Read only access to root namespace (/) and super user ( ROOT) access to volume namespace to scan NFS exports. If the root namespace and volume are configured with two different export policies, then you must provide access to the Information Governance Collector under each export policy rules to enable Information Governance to scan the NFS shares.
To enable export of NFS shares on a NetApp Cluster-Mode file server
- To verify whether the Information Governance Collector IP address is specified in the export policy rule, execute the following command.
export-policy rule show -vserver <name of vserver> -policyname <export policy> -clientmatch <IP of Information Governance Collector>
The command must be repeated if root namespace is configured to use different export policies.
- The following command will display a denied access message if the IP address of the Collector host is not specified in the export policy rule.
export-policy check-access -vserver <vserver name> -volume <volume name> -client-ip <collector IP of DI> -authentication-method sys -protocol nfs3 -access-type read
- If the Information Governance Collector is not specified in the export policy, modify the export policy rule. Run the following command:
export-policy rule modify -vserver <name of vserver> -policyname <export policy> -clientmatch <IP of Information Governance Collector>
- To validate the access given, run the following command and check read/write access is shown:
export-policy check-access -vserver <vserver name> -volume <volume name> -client-ip <collector IP of DI> -authentication-method sys -protocol nfs3 -access-type read-write
NFS share type will be based on the configured export policy protocol. Refer to the table below for details:
Export policy protocol | MSU Type |
---|---|
NFSV4 | NFSV4 |
NFSV4, NFS | NFSV4 |
NFSV3, NFSV4 | NFSV3 |
ANY or Select all | NFSV3 |
Note:
You need to run rediscovery for device if any changes are made in export policy on NetApp Cluster.
In Kerberos environment, default scanning will try to mount shares using Kerberos. If you do not have Kerberos environment, you can create one by adding kerberos.enabled in the advance setting custom property of the collector with value as false.