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 a generic storage device options
Use this dialog box to add a new generic storage device to Arctera Insight Information Governance or to edit the configuration of an existing device.
Table: Add/Edit generic device options
Field | Description |
---|---|
Filer hostname or IP address | Enter the hostname or IP address of the device that you want Information Governance to monitor. |
Collector | Do the following:
Information Governance connects to the filer from this server. It is recommended that the Collector worker node share a fast network with the filer. Note: When monitoring NFS shares, ensure that the Collector node monitoring the filer must have services for NFS enabled as file server roles. You can install the role on a supported version of Windows through the > option.Changing the Collector If you want to change the existing collector, you will lose events during collector migration, impacting the incremental scan. It is recommended that you initiate migration during the maintenance window. Prior to initiating the collector migration, make sure the following conditions are met:
|
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. |
Enable CIFS Monitoring | Check this box to enable monitoring of CIFS shares. |
Enable NFS Monitoring | Check this box to enable monitoring of NFS exports. |
Filer Administrator Credentials | Specifying the filer administrator credentials to enable share discovery. |
Share Configuration | Check Discover shares automatically to allow Information Governance 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. |
Filer does not belong to a domain | Check this box if the filer belongs to other domain. Note: This option is available only if NFS Monitoring is enabled. |
Domain | From the drop-down, select the domain to which the device belongs. This option is enabled when monitoring NFS shares. |
Enable filer scanning | Select the check box to enable filer scanning according to the specified schedule. |
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. |
Test credentials | Do the following:
|
Scanner credentials | |
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. |
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. 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. |