Search <book_title>...

Important Update: Cohesity Products Documentation

All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.

Arctera Insight Information Governance Administrator's Guide

Last Published: 2025-11-24

Product(s): Data Insight (7.2)

Platform: Windows

Section I. Getting started
1. Introduction to Arctera Insight Information Governance administration
  1. About Arctera Insight Information Governance administration
    1. Operation icons on the Management Console
    2. Information Governance administration tasks
2. Configuring Information Governance global settings
Section II. Configuring Information Governance
Section III. Configuring native file systems in Information Governance
Section IV. Configuring SharePoint data sources
1. Configuring monitoring of SharePoint web applications
2. Configuring monitoring of SharePoint Online accounts
Section V. Configuring cloud data sources
Section VI. Configuring Object Storage Sources
1. Amazon S3
Section VII. Health and monitoring
1. Using Arctera Insight Information Governance dashboards
2. Monitoring Information Governance
Section VIII. Alerts and policies
1. Configuring policies
Section IX. Remediation
1. Configuring remediation settings
Section X. Reference

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:

ONTAP 9.14.1
- You will have to manually create and configure a volume and then create a persistent store for the newly created volume.
- If a persistent store already exists, use the same persistent store name for fpolicy creation in Information Governance.
ONTAP 9.15.1
- When you create the persistent store, ONTAP automatically creates and configures its volume at the same time.
- If a persistent store already exists, Information Governance automatically uses the same persistent store name for fpolicy creation.

Configuring Persistent Store for ONTAP 9.14.1

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 like Information Governance Collector. 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
- 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.

For Persistent Store for ONTAP 9.15.1 onwards

If the persistent store does not exist, Information Governance will create a new persistent store named datainsight_ps_<SVM Name>, along with a volume named datainsight_psvol_<32-bit MD5 hash of SVM Name>, with a default volume size of 1 GB.
You can modify the persistent store volume size by editing the fpolicycmod.conf file located in the Datadir/conf folder on the Collector.
The fpolicycmod.conf file on the Collector contains the following configuration:fpolicy.persistentstore.volume.size=1073741824. In this configuration, fpolicy.persistentstore.volume.size is the property name, and 1073741824 (in Bytes) represents the volume size.