Search <book_title>...

Veritas CloudPoint Administrator's Guide

Last Published: 2019-11-18

Product(s): CloudPoint (2.2.1)

Platform: Linux

How to use tag-based asset protection feature

Using the tag-based asset protection feature involves the following steps:

Table: Using tag-based asset protection

Step #	Action
Step 1 - Create protection policies	Create one or more CloudPoint protection policies with the desired snapshot and replication settings and a policy schedule. Ensure that you create the appropriate host or disk-level policy depending on the type of asset that you wish to protect. Make a note of the policy names. You are going to use the policy names in the tags that you create and assign to the assets. See About policies.
Step 2 - Add tags to the assets	Using the cloud vendor management tools, add tags to the assets that you wish to protect using the configured CloudPoint policies. The tags must be defined as a `"key":"value"` pair and must use the following convention: "veritas-protection-policy":"`<policyname>`" Here, `veritas-protection-policy` is the name of the key. `<policyname>` is the value of the key and represents the CloudPoint protection policy that you wish to associate with the asset. For example, if the name of the policy is `Policy1`, the asset tag will be as follows: "veritas-protection-policy":"Policy1" Note: The key name and the value are not case sensitive. If you want to associate multiple protection policies to the same asset, you can specify all the policies within a single tag. This is the most critical step in the process. If the assets are not tagged correctly, the feature will not work.
	In case of AWS and Azure cloud assets, specify multiple policy names separated using commas. For example, if want to associate policies `Policy1`, `Policy2`, and `Policy3`, the asset tag will be as follows: "veritas-protection-policy":"Policy1, Policy2, Policy3" In case of GCP cloud assets, specify multiple policy names separated using the underscore character. For example, using the same policy names listed earlier, the asset tag will be as follows: "veritas-protection-policy":"Policy1_Policy2_Policy3"
Step 3 - Configure the CloudPoint plug-in	Configure the CloudPoint plug-in for the desired cloud environment (AWS, GCP, or Azure). See About plug-ins. When you configure the plug-in, CloudPoint immediately begins discovering the assets in that cloud and starts scanning the tags associated with the discovered assets. If an asset tag matches an existing CloudPoint policy name, CloudPoint automatically starts protecting that asset through the matching protection policy as per the policy schedule. If the asset tag does not match with any existing policy name, a notification is generated informing that the policy does not exist. However, if a policy by that name is created later, CloudPoint automatically starts protecting that asset through the matching policy as per the policy schedule.

The order of the tasks mentioned in the table does not matter. You do not need to perform these tasks in a sequential manner. All that is required is that you create the CloudPoint policy and ensure that the corresponding tag is associated with the asset that you wish to protect.

For example, you can add tags to the assets even before you install and configure CloudPoint. Once you have installed CloudPoint and configured the plug-in, you can create the requisite protection policies. During the discovery cycle, CloudPoint checks the asset tags and automatically starts protecting the asset through the matching policy as per the policy schedule.

Similarly, if you have already deployed CloudPoint, you can add appropriate tags to new assets that are not yet discovered by CloudPoint. During the discovery cycle, CloudPoint scans all the assets and their tags and automatically starts protecting those assets through a matching policy.