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
About migrating storage devices across Indexers
Every storage device that is configured in Information Governance has exactly one Indexer node associated with it. The Indexer node processes the audit data from the Collector to service queries from the Management Server.
You may consider migrating a storage device to another Indexer in the following situations:
If the existing Indexer for the storage device displays high resource utilization and the backlog of files being processed starts accumulating on the node. Migrating to another Indexer helps balance the load on the existing Indexer.
See Monitoring the performance of Information Governance servers.
If the existing Indexer is being decommissioned.
If you want to migrate from a Windows server to a Linux server.
Before you decide to migrate the storage device to another Indexer, ensure the following:
Both the source and the destination Indexers are in good health and can communicate with each other using the fully qualified domain name. Ensure that port 8383 is open between the indexers to allow the Communication Service to communicate between them.
The destination Indexer has enough disk space, CPU, and memory capacity to take the additional load.
The Collector nodes that are associated with the storage device have enough disk space, because the files may accumulate on the Collector nodes during the migration.
All classification requests involving the source Indexer are in Completed state. Pending and in-progress classification requests are cancelled during the migration.
The migration should take place during quiet hours, so that additional files for consumption are not flowing in rapidly.