Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- About the deployment approach
- Deciding where to run CloudPoint
- Meeting system requirements
- CloudPoint host sizing recommendations
- Creating an instance or preparing the physical host to install CloudPoint
- Installing Docker
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- 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
- Dell EMC Unity array plug-in configuration notes
- Pure Storage FlashArray 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
- Configuring an off-host plug-in
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- About agents
- Oracle plug-in configuration notes
- MongoDB plug-in configuration notes
- Microsoft SQL plug-in configuration notes
- About the installation and configuration process
- Preparing to install the Linux-based on-host agent
- Preparing to install the Windows-based on-host agent
- Downloading and installing the on-host agent
- Configuring the Linux-based on-host agent
- Configuring the Windows-based on-host agent
- Configuring the on-host plug-in
- Configuring VSS to store shadow copies on the originating drive
- 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
- About snapshot replication
- About cross-account snapshot replication in the AWS cloud
- Requirements for replicating snapshots
- Cross-account snapshot replication support matrix
- Cross-account snapshot replication limitations
- Configuring replication rules
- Editing a replication rule
- Deleting a replication rule
- Managing your assets
- Creating a snapshot manually
- Displaying asset snapshots
- Replicating a snapshot manually
- About snapshot restore
- About single file restore (granular restore)
- Single file restore requirements and limitations
- Restoring a snapshot
- Additional steps required after restoring disk-level snapshots
- Additional steps required after a SQL Server snapshot restore
- Additional steps required after an Oracle snapshot restore
- Additional steps required after a MongoDB snapshot restore
- Additional steps required after restoring an AWS RDS database instance
- Restoring individual files within a snapshot
- Deleting a snapshot
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Restarting CloudPoint
- Docker may fail to start due to a lack of space
- CloudPoint installation fails if rootfs is not mounted in a shared mode
- Some CloudPoint features do not appear in the user interface
- Off-host plug-in deletion does not automatically remove file system and application assets
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Snapshot restore for encrypted AWS assets may fail
- Error while adding users to CloudPoint
- CloudPoint fails to revert restored snapshots if indexing, classification, or restore operations fail
- SQL snapshot or restore and SFR operations fail if the Windows instance loses connectivity with the CloudPoint host
- Troubleshooting CloudPoint logging
- Swagger UI-based authorization for CloudPoint REST API calls may fail
- Policy retention count is not honored for file system and application assets if there is an issue with the CloudPoint plug-in
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Unconfiguring the CloudPoint agent
To enable CloudPoint to protect assets on a remote host, you first need to establish a connection between the CloudPoint server and the remote host. Depending on how the connection is configured (either using on-host agents or the agentless feature), CloudPoint uses agents and plug-ins to discover all the assets on the host.
Whenever you configure a remote host for protection, the agent registration and the plug-in configuration information is added to the CloudPoint database on the CloudPoint server. You can, if required, remove an agent entry from the CloudPoint database by performing the disconnect operation from the CloudPoint UI.
Before you unconfigure an agent, consider the following:
Once you unconfigure an agent, you cannot re-configure a CloudPoint plug-in on the same host, if you had installed the CloudPoint on-host agent on that host. To be able to configure a plug-in on the host again, you must first uninstall the agent package from the host, connect the host and install and register the agent with the CloudPoint server again.
You must first unconfigure the CloudPoint plug-in from the host before you proceed with the disconnect operation. The disconnect option is not enabled if a CloudPoint plug-in is configured on the host.
Unconfiguring an agent entry from the CloudPoint server does not uninstall the agent package from the host. You have to manually remove the agent binaries from the host after completing the disconnect operation.
Once you unconfigure an agent, all the file system assets that belong to that host are removed from the CloudPoint configuration. The assets no longer appear in the CloudPoint UI.
To unconfigure the agent entry from the CloudPoint server
- Sign in to the CloudPoint UI.
- Remove CloudPoint plug-in configuration from the host that you wish to disconnect.
- On the dashboard, under the Environment section, locate the Hosts area, and then click Manage.
- On the Asset Management page, select the host where you want unconfigure the agent and then from the Asset Details panel on the right, click Disconnect.
- On the confirmation dialog box, click Disconnect.
CloudPoint begins to unconfigure the agent. Observe that the Disconnect button now changes to Connect. This indicates that the disconnect operation is successful and the agent has been unconfigured successfully.
The agent registration and all the assets information about that host is completely removed from the CloudPoint database.
- The next step is to manually uninstall the agent from the host on which you performed the disconnect operation. This is required if you wish to protect this host and its assets using CloudPoint at a later time.