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
Preparing Information Governance to receive event notification
The EMC Common Event Enabler (CEE) can be installed on the same Windows server as the Information Governance Collector node or on a remote server in the same Active Directory domain.
You must perform the following steps to route events from the Windows server on which the EMC CEE is installed to the Collector node.
To prepare Information Governance to receive event notification
- Provision a supported version of Windows server to run the EMC CEE framework in the same Active Directory domain as the filers you want to monitor.
- Open Windows' Registry Editor (Start > Run > regedit).
- In Registry Editor, navigate to
HKEY_LOCAL_MACHINE > SOFTWARE > EMC > CEE > CEPP > Audit > Configuration
. - Double-click Endpoint.
- Modify the registry entry for the EMC CAVA service to allow access to the Information Governance Collector node. Depending on the type of your Information Governance deployment, there can be the following different scenarios:
The EMC CAVA service and the Collector node are running on the same machine, and the EMC CAVA service is only being used by Information Governance. In this case, add the Information Governance key, SymantecDataConnector, to the Endpoint option.
The EMC CAVA service and the Collector node are running on the same machine, and the EMC CAVA service is also being used by applications other than Information Governance. In this case, append the Information Governance key, SymantecDataConnector, to the Endpoint option. Each entry must be separated by a semi-colon.
Note:
The above-mentioned scenarios are automatically configured at the time adding filers.
The EMC CAVA service and the Collector node are running on separate machines, and the EMC CAVA service is being used only by Information Governance. In this case, add the Information Governance key in the format, SymantecDataConnector@<IP address of the Collector>, to the Endpoint option.
The EMC CAVA service and the Collector node are running on separate machines, and the EMC CAVA service is also being used by applications other than Information Governance. In this case, append the Information Governance key in the format, SymantecDataConnector@<IP address of the Collector>, to the Endpoint option.
If the EMC CAVA service is installed on multiple machines, modify the registry entries on each of these machines.
- Double-click the Enabled setting, and set its value to 1.
- To start the EMC CAVA service, run the following command on the EMC filer to check the service status. For example,
Server_cepp server_2 -pool -info
- Install Information Governance Collector node.
- Log in to the Information Governance Management Console.
- Navigate to Settings > Servers to open the Servers details page for the Collector.
- Navigate to the service configuration section on the filer, and click Enable to start the DataInsightCelerra service on the Collector node.
- Under Credentials, enter the credentials that the service needs to run as. The specified credentials must be that of a domain user.
- Click Configure to apply these settings to the server and start the EMC CAVA service.