1. Support
  2. Knowledge base
  3. 100050089

How Policies Work in Veritas Alta SaaS Protection

Article: 100050089
Last Published: 2023-09-07
Ratings: 0 0
Product(s): Veritas Alta SaaS Protection

Description

Veritas Alta SaaS Protection executes policies on a near-real time basis. You never have to worry about scheduling your policies. Simply create them, and within a few minutes of applying any changes your policies will automatically run.
 
This article will discuss some of the general features of Veritas Alta SaaS Protection policies, and will walk you through an example of how to configure a policy.

Types of Policies in Veritas Alta SaaS Protection

The types of policies are:
  • Retention
  • Tagging
  • Indexing

Each policy automatically maintains statistics about the content matching the policy's selection criteria.

In Veritas Alta SaaS Protection, things like legal hold, searches added to a case, RegExs, and other types of jobs all leverage the policy evaluation and action executor frameworks.

Policies Operate at the Stor Level

The boundary of each policy is the Stor. You'll notice when creating Indexing policies that it is done within the context of a Stor's configuration, and when you create Retention and Tagging policies that there is a drop down menu to select which Stor they will apply to.

Policy Execution Interval

You can control how often policies run on each Stor. To see or modify this setting, click to the 'Administration' area then select the Stor.

Under the 'General' tab of each Stor you will see an 'Advanced' section with a setting to control the number of minutes Veritas Alta SaaS Protection must wait before re-executing policies.

NOTE: It is generally a good idea to keep this setting at 10 to 15 minutes. A Stor that is routinely ingesting new content, contains high item counts, and has many policies may require a higher performance class of database for more aggressive intervals.

Example: How to Configure a Veritas Alta SaaS Protection Policy

The following example will show you how to create and configure an Veritas Alta SaaS Protection policy. This instruction can be applied to Retention, Tagging, and Indexing policy types.

To create a new policy, click ' Add Policy'.
 
 
Then, set the Action Mode to either Preview or Production.
  • Preview -- This mode executes your policy without applying any actions. It is usually a good idea to run policies in 'Preview' mode to start so that you can see the data that will be affected when you switch into 'Production' mode.
  • Production -- This mode executes your policy along with any actions. Whatever content meets your policy's selection criteria will have the policy's action applied.
     
 
Finally, decide if your policy will be 'Enabled' or not. When 'Enabled' is not checked, your policy will not run during policy evaluation.

Click ' Apply' to create your policy.

With your policy created, you will now need to add one or more clauses to it to define the policy's selection criteria. To do this, expand the policy, select the ' Selection Criteria' tab, and click the ' Add Clause' button.
 
 
Clicking 'Add Clause' will present a list of the available clauses that can be used in the policy. Select one and click ' Apply'.

 
After adding one or more clauses, you will need to configure them. To configure a clause, click the edit icon beside the clause you wish to configure.
 
 
This will present the ' Edit Policy Clause' window. This window will be specific to the clause type that you are editing. For instance, for 'DataOwner', 'Include Custodians', and 'Exclude Custodians' clause types, you will pick a principal (user or group); for LastAccessed and LastModified you will specify either a specific range, date range, or metadata value.  After you configure the clause, click ' Apply'.

Example of a date range configuration on a LastAccessed policy clause:
 
 
Click ' Apply' when you are done editing the policy clause.

If you need to modify the clause's criteria, simply select the edit icon again.

If you need to remove a clause from a policy, click the delete icon next to the clause you wish to remove.
 
 
Finally, to save your policy, click the ' Apply' button at the bottom right of the 'Full-Text Index Settings' tab page.
 

Change the Policy's Name and Settings

At any time, you can edit the name and settings of your policy by clicking the edit icon beside the policy name.


Delete a Policy

At any time, you can delete a policy by clicking the delete icon beside the policy name.


NOTE:  As of ASP 2.18 simply deleting a Tagging Policy will leave orphaned tags on tagged data that cannot be removed from the data in the Admin Portal. It would be better to disable the tagging policy. Or remove the tags from the data before deleting the tagging policy. For more details, review the article How to remove tags from content that were applied by a Tagging Policy.  

 

Was this content helpful?

Article Languages