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
Add/Edit NetApp cluster file server options
Use this dialog box to add a new NetApp filer in cluster mode to Arctera Insight Information Governance or to edit the configuration of an existing filer.
Table: Add/Edit NetApp cluster file server options
Field | Description |
---|---|
Cluster Management Host | Enter the host name or IP address NetApp Cluster Management host interface that is used to manage the nodes in the cluster. |
Collector Use Collector Pool for Scanning | Do the following:
Information Governance connects to the NetApp Cluster Management host from this server. Arctera recommends that the Collector worker node share a fast network with the cluster management host. On collector selection page, Select Collector pop-up will display Linux Collector as well, which can be identified from Operating System Column. Check the Use Collector Pool for Scanning box if you want to assign a collector pool. The Collector Pool is typically treated as a single logical unit for load balancing, high availability, or scalability purposes. See About Server Pools. for more details. Enter a number in the Maximum number of shares to scan in parallel field. Maximum number of shares to scan in parallel is a configuration setting that controls how many file shares (like SMB/CIFS shares) the system scans simultaneously for a specific filer. Higher values can increase scanning speed but may consume more CPU and network bandwidth while lower values reduce resource usage but may slow down scanning. Set this value based on the filer's performance capacity and network conditions. |
Indexer | Do the following:
Events and metadata that are collected from the cluster are processed and stored on the Indexer node. You can also migrate the file server to another Indexer. |
Cluster Management Interface credentials | Information Governance uses the credentials that you specify to discover the following:
To enable Information Governance to successfully discover shares, ensure that HTTP port 80 is not blocked between Information Governance Collector and NetApp cluster management host. Specifying the filer administrator credentials is optional, if you choose to not monitor events on the filer, nor enable share discovery. See Credentials required for configuring a clustered NetApp file server. |
Cluster Management SSL Certificate | Optionally, you can use an SSL certificate instead of the Cluster Management Interface credentials.
Note: If you choose to use SSL authentication, use local user credentials. Do not choose this option if you are using domain user credentials to configure the NetApp cluster-mode filer. The SVMs with NFS protocol enabled are not be discovered if you are using domain user credentials authenticated using SSL. |
Test credentials | Click to test the availability of network connection between the Collector worker node and the filer, and to test the validity of specified credentials. Arctera recommends that you test the connection before proceeding to ensure that Information Governance is able to connect to the cluster management host. By default, Information Governance does not test credentials for the following HOMEDIR shares:
|
CIFS Server / Storage Virtual Machine (SVM) | Every SVM node in the cluster has a CIFS server configured on it. The CIFS server represents a file server for Information Governance. If both CIFS and NFS protocols are enabled, Information Governance automatically discovers the CIFS server name. If only CIFs protocol is enabled, Information Governance discovers all the CIFS servers that are configured in the cluster. If only NFS protocol is enabled then Information Governance fetches the SVM name. From the drop-down, select the CIFS server/SVM that you want Information Governance to monitor. Ensure that you can resolve the CIFS server host name from the Collector node. Note: For Linux Collector, SVMs which supports NFS protocol will be discovered. Any SVM supporting CIFS and NFS will be discovered but monitoring will be done only for NFS . If you select Linux Collector, SVMs which supports NFS protocol will be discovered. Any SVM supporting CIFS and NFS both will be discovered but only NFS monitoring will be done. |
Storage Virtual Machine (SVM) Alias | Information Governance can exclusively support CIFS on Windows collector and NFSv4 on Linux Collector. However, NFSv3 can be supported on both Windows and Linux Collector. To support a SVM which is having hybrid configuration of CIFS + NFSv4 load or CIFS + NFSv3 or CIFS + NFSv3 + NFSv4, Information Governance will allow addition of same SVM again on different OS collector using Alias functionality. Based on various conditions mentioned in below table CIFS Server / Storage Virtual Machine (SVM) drop-down can also show SVM which is already added in Information Governance. If you select that SVM, a new free-text box will be visible to add Storage Virtual Machine (SVM) Alias. This SVM will be saved in Information Governance with that alias name and will be used with that alias name at all other places in Information Governance. If you are saving a SVM with an alias name based on type of monitoring enabled, Use CIFS Data LIF hostname for scanning / Use NFS Data LIF hostname for scanning options will become mandatory. For more information about the Storage Virtual Machine (SVM) Alias, refer to the table at the end of this section. |
Enable CIFS Monitoring | Check the box to monitor CIFS shares. This checkbox will be disabled for Linux Collector. |
Enable NFS Monitoring | Check the box to monitor NFS exports on the Isilon. |
Select Domain | Select domain from the drop-down. |
Use CIFS Data LIF hostname for scanning (Optional) / Use NFS Data LIF hostname for scanning | You can use a Logical Interface (LIF) associated with the SVM to communicate with Information Governance. Information Governance uses the Data LIF to access data from the CIFS and NFS servers . If the Admin LIF and Data LIF are associated with two different networks, then you must specify the Data LIF name while scanning the CIFS shares or NFS exports that reside on configured CIFS servers. Providing a Data LIF hostname is also useful if the Admin LIF for the cluster is not configured for CIFS or NFS protocol access. Selecting the LIF hostname is optional if the name of the CIFS server and the Data LIF is the same. Note: This option will be disabled for Linux Collector. Use CIFS Data LIF hostname for scanning option will be disabled in case Linux Collector is selected. |
Discover shares automatically | Check the box to allow Information Governance to automatically discover shares of the filer and add them to the configuration. Discovery of shares takes place as soon as you add a new filer and then twice each day at 2:00 A.M. and 2:00 P.M. You can also choose to add shares manually. |
Exclude shares from discovery | Enter the details of shares which should not be included during discovery. This option is available if you select |
Enable storage utilization analytics | Select the check box to allow Information Governance to gather storage utilization information from the filer. This information is used when you generate Filer Utilization and Filer Growth Trend reports. Note: The Filer utilization and Filer Growth Trend reports are available only for NetApp and Windows File Server. The DataInsightFpolicyCmod service running on the Collector node gathers information about storage utilization on the filer. |
Enable file system event monitoring | Select to enable event monitoring on the filer. |
Enable FPolicy automatically | Select to automatically enable FPolicy on the filer. Once you enable FPolicy, the Clustered Data ONTAP SVM node server initiates a TCP connection to the Information Governance FPolicy server. Ensure that the communication port in the firewall between the FPolicy server and the cluster management host is open. If you clear this check box, you must manually enable FPolicy on the filer. |
Register for security events | Select if you want Information Governance to monitor the changes to permissions in your storage environment. By default, this option is not selected because it has a significant impact on the performance of the file server. |
Enable filer scanning | Select the check box to enable filer scanning according to the specified schedule. |
Scan new shares immediately | Select this option to scan newly added shares immediately, instead of waiting for the normal scan schedule. Scanning proceeds only when scanning is permitted on the Collector node. |
Scanner credentials | See Credentials required for configuring a clustered NetApp file server. This option will not be available for Linux Collector. |
Scanning schedule for full scans | Select one of the following to define a scanning schedule for shares of this filer:
Arctera Insight Information Governance periodically scans shares of the filer to obtain file metadata and security descriptors. Each Collector worker node by default initiates a full scan of shares at 7:00 P.M. on the last Friday of each month. |
Details about the Storage Virtual Machine (SVM) Alias are as follows:
SVM Type | Previous Collector OS | Current Collector OS | Alias Visible | Notes |
---|---|---|---|---|
CIFS ONLY | Windows | Windows | No | Already added on Windows |
CIFS ONLY | Windows | Linux | No | CIFS is not supported on Linux |
NFS Only | Windows | Linux | Yes | Allowing as it can have NFSv4 shares which are not supported on Windows |
NFS Only | Linux | Windows | No | As already added on best supported OS |
NFS Only | Windows | Windows | No | Already added on Windows |
NFS Only | Linux | Linux | No | Already added on Linux |
CIFS + NFS | Windows | Linux | Yes | Allowing as it can have NFSv4 shares which are not supported on Windows |
CIFS + NFS | Linux | Windows | Yes | Only CIFS monitoring is allowed |