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
 
Removing CloudPoint plug-in configuration
Before you upgrade CloudPoint, you must remove the CloudPoint plug-ins that are no longer supported by the newer CloudPoint release. If you upgrade CloudPoint without removing the deprecated plug-ins, then CloudPoint may hang and you may not be able to log on to the CloudPoint UI after the upgrade.
For example, the HPE 3PAR plug-in was deprecated beginning CloudPoint 2.2 release. If you have configured the plug-in in your CloudPoint environment, you must remove it before you upgrade to CloudPoint 2.2 or a later release.
To remove a CloudPoint plug-in
- Ensure that you there are no active snapshots of the assets that are managed by the CloudPoint plug-in. You cannot remove a CloudPoint plug-in if there are snapshots.
For example, if you want to remove the HPE 3PAR plug-in, ensure that you delete all the CloudPoint snapshots from the HPE 3PAR array.
See Deleting a snapshot.
 - From the CloudPoint dashboard, in the Administration card, locate Clouds/Arrays and then click Manage.
 - On the Clouds and Arrays page, select the CloudPoint plug-in that you wish to remove and then click Manage from the Plugin Details panel that appears on the right side.
 - On the plug-in configurations page, select the plug-in configuration and then click Remove Configuration from the Configuration Details panel that appears on the right side.
 - Respond to the dialog that asks you to confirm whether you want to remove the plug-in configuration.
The UI displays a message that the plug-in has been removed successfully.
 - Repeat these steps for each deprecated CloudPoint plug-in that you wish to remove.
 - The next step is to upgrade CloudPoint.
See Upgrading CloudPoint.