Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Tag-based asset protection considerations and limitations
The following conditions are applicable to the tag-based asset protection feature:
Tag-based asset protection is offered as a Technical Preview feature. It should not be used in a production environment.
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 assigned to a CloudPoint protection policy until the assets are discovered by CloudPoint.
You cannot modify a policy name if the policy is associated with a tagged asset using tag-based asset protection.
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.
Tag-based asset protection feature will not take effect if the same policy is manually assigned to the tagged asset earlier. For example, consider a policy
Policy1
that is manually assigned to an assetVM1
. Now, even if you add a tag"veritas-protection-policy":"Policy1"
toVM1
, CloudPoint ignores that tag and does not reassign the policy to that asset again. The policy association is considered as manual and tag-based asset protection functionality does not take effect on that asset or policy.All tag-based asset protection operational logs are stored in the
flexsnap-policy
andflexsnap-coordinator
logs.