Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight 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 Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
About migrating storage devices across Indexers
Every storage device that is configured in Data Insight 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.
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 canceled during the migration.
The migration should take place during quiet hours, so that additional files for consumption are not flowing in rapidly.