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
- Hitachi plug-in configuration notes
- InfiniBox 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
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Off-host plug-in deletion does not automatically remove file system and application assets
When you configure an off-host plug-in, CloudPoint immediately starts discovering all the assets that are associated with that plug-in. For example, in case of the AWS plug-in, CloudPoint discovers all the EC2 instances and the corresponding EBS volumes that are being used.
However, for CloudPoint to be able to discover the file systems and applications on those instances, you are also required to configure the CloudPoint on-host plug-in or the agentless feature. From the CloudPoint UI, you have to connect to each of the instances and then click Configure.
When you remove the off-host plug-in, CloudPoint automatically removes the discovered instances and storage assets that are associated with that plug-in. For example, in case of AWS plug-in, an EC2 instance and the corresponding EBS volumes are removed from the CloudPoint configuration.
However, the off-host plug-in deletion does not automatically remove the file system and application assets that belong to the on-host or agentless host instances corresponding to the off-host plug-in. Those assets are discovered by the on-host plug-ins or the agentless feature and remain in the CloudPoint configuration even after the off-host plug-in is deleted.
On the Asset Management page in the CloudPoint user interface (UI), the Snapshotable column for such assets displays as No. You may not be able to perform any snapshot operations (for example, create snapshot, view snapshot) on such file system and application assets.
Workaround:
After deleting the off-host plug-in, you also have to manually remove the on-host agents and plug-ins and the agentless feature to cleanup all the associated assets from the CloudPoint configuration.
You can remove agents and plug-ins using the following CloudPoint APIs:
Table: CloudPoint APIs: Delete agents and plug-ins
Objective | HTTP Method | API URI |
---|---|---|
Delete an agent | DELETE | /v3/agents/{agentId} |
Delete a plug-in from an agent | DELETE | /v3/agents/{agentId}/plugins/{pluginName} |
Delete a configuration entry for a plug-in | DELETE | /v3/agents/{agentId}/plugins/{pluginName}/configs/{configId} |