Arctera Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Arctera Data Insight administration
- Configuring Data Insight global settings
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight 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 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
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp 7-mode 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 7-mode 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 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
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Data Insight best practices
- Appendix B. Migrating Data Insight components
- Appendix C. Backing up and restoring data
- Appendix D. Data Insight health checks
- About Data Insight health checks
- About Data Insight health checks
- Appendix E. Command File Reference
- Appendix F. Data Insight jobs
- Appendix G. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Persistent Store
FPolicy allows you to set up a Persistent Store (PS) to capture file access events for asynchronous non-mandatory policies in the SVM. This mode decouples client file operations and FPolicy event processing to help reduce client latency. Once enabled, FPolicy will write the event to a pre-configured persistent volume to release the file operation. Simultaneously, FPolicy will process the events store in the volume to create notifications, which will be sent out to the external FPolicy server(s).
Note:
Persistent Store is not supported for versions prior to 9.14.1
Note the following points:
If a persistent store exists, use the same persistent store name for fpolicy creation.
If there is no persistent store for version 9.14.1, create a new persistent store for the selected SVM using the steps given below.
For ONTAP version 9.14.1, only existing persistent stores will be used. There will be no provision to create a new one.
To configure Persistent Store manually,
- Create a volume on the SVM that can be provisioned as the Persistent Store.
volume create -vserver <SVM Name> -volume <volume> -state <online> - junction-path <path> -policy <default> -unix-permissions <777> -size <value> -aggregate <aggregate name> -snapshot-policy <none>
Size of the Persistent Store volume is based on the time duration for which you want to persist the events that are not delivered to the external server (partner application). For example, if you want 30 minutes of events to persist in a cluster with 30K notifications per second capacity: Required volume size = 30000 x 30 x 60 x 0.6KB (avg notification record size) = 32400000 KB = ~32GB
To find the approximate notification rate, you can either reach out to your FPolicy partner application or utilize the FPolicy counter 'requests_dispatched_rate'.
It is expected that an admin user with sufficient RBAC privilege (to create a volume) will create a volume (using the volume CLI command or REST API) of the desired size and provide the name of that volume as the -volume in the Persistent Store create CLI command or REST API.
Enable FPolicy, unmount the volume in ONTAP to remove the junction path, to ensure Persistent Store volume is inaccessible to external user protocol access (CIFS/NFS) and avoid accidental corruption or deletion of the persisted event records.
The snapshot policy is set to none for that volume instead of default. This is to ensure that there is no accidental restore of the snapshot leading to loss of current events and to prevent possible duplicate event processing.
- Create the Persistent Store using the following command:
vserver fpolicy persistent store create -vserver <SVM> -persistentstore <PS_name> -volume <volume>
persistent-store: The Persistent Store name
volume: The Persistent Store volume
- After the Persistent Store is created, you need to create the FPolicy policy and add the Persistent Store name to that policy.
vserver fpolicy policy create -vserver-name vserver_name -policy-name policy_name -engine engine_name -events event_name, [-persistentstore PS_name] [-is-mandatory {true|false}] [-allow-privileged-access {yes|no}] [-privileged-user-name domain\user_name] [-is-passthroughread- enabled {true|false}]
- The remaining configuration for events, external engine and scope has no new alternation.