Veritas CloudPoint Administrator's Guide

Tag-based asset protection works only for assets that support associating tags. If the assets cannot be assigned a tag in the form of a key:value pair, then you cannot use the CloudPoint tag-based asset protection for those assets.

You will have to manually assign CloudPoint policies to protect such assets.

The CloudPoint user interface (UI) does not support configuring tag-based asset protection. You will not be able to see the tags that are assigned to the assets or administer this feature from the UI.

Tags must be assigned to the assets using the cloud vendor management tools.

Newly created tagged assets are not protected by a CloudPoint protection policy until the assets are discovered by CloudPoint.

You cannot modify a policy name if the policy is actively protecting assets based on the "veritas-protection-policy" tag.

You cannot delete a policy if the policy is associated with a tagged asset using tag-based asset protection. To delete a policy, you must remove the policy name from the "veritas-protection-policy" key value (in case multiple policies are specified in the tag), or delete the key if there are no other policies specified in the asset tag.

You cannot manually disassociate a policy from a tagged asset if the policy is assigned using tag-based asset protection.

You must first remove the policy name from the asset tag or delete the asset tag altogether. After the next discovery cycle, CloudPoint automatically removes the asset from that policy in a subsequent policy run.

All tag-based asset protection operational logs are stored in the flexsnap-policy and flexsnap-coordinator logs.