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
Advanced configuration parameters for Hitachi NAS
Sometimes the file operations per seconds (FOPS) for a Hitachi NAS filer may be affected once Information Governance starts fetching events. Information Governance introduces an idle period between two successive read calls to let the filer improve the speed of file operations.
You can configure the following parameters to tune Hitachi NAS filer:
max_events_to_pull | Specifies the maximum number of raw events fetched by Information Governance per execution of Default value is 300000. |
max_valid_events | Specifies the maximum number of events that can be stored in the Information Governance audit database. Default value is 100000. |
min_events_per_run | For all the read calls which fetch less number of events than min_events_per_run, Information Governance sleeps for sleep_per_run microseconds, before making next read call. Default value is 100. You can set this parameter to fetch events at an optimized rate which does not degrade the performance of the filer. If the number of events to be fetched is too high, some of the events might be lost. In a single invocation of audit utility Information Governance makes read calls till it finds no new events to be fetched. |
sleep_per_run (in microseconds) | Specifies the amount of time by which Information Governance waits between two successive read calls if the minimum number of events fetched per read call decreases below the value specified by the min_events_per_run parameter Default value is 500000 microseconds (0.5 seconds). |
max_audit_interval (in minutes) | Specifies the approximate time interval after which audit file would be generated. Default value is 10 minutes. |
To alter the configuration parameters, you can use configdb.exe command from the Information Governance Management Server.
For example:
configdb.exe -o -T filer -k 2 -J max_events_to_pull -j 50000
Where,
o- Object attribute
k- Filer ID
J- Attribute name
j- Attribute value