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
Backing up CloudPoint
To back up CloudPoint when it is deployed in a cloud
- Sign out of the CloudPoint user interface (UI).
- Stop CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name: /full_path_to_volume_name -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version stop
Here, version represents the currently installed CloudPoint product version.
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.0.1.5300 stop
Note:
This is a single command. Ensure that you enter the command without any line breaks.
Use the following API to determine CloudPoint version installed and configured on your setup:
# curl -H "Content-Type: application/json" -H "Authorization: Bearer $token" -X GET -k https://localhost/cloudpoint/api/v3/version
Use the following API to get the CloudPoint authentication token:
# curl -k -X POST -H 'Content-type: application/json' -d '{"email": "<email>", "password": "<pass>" }' -k https://localhost/cloudpoint/api/v3/idm/login/
- Make sure that all CloudPoint containers are stopped. This step is important because all activity and connections to and from CloudPoint must be stopped to get a consistent CloudPoint backup.
Enter the following:
# docker ps | grep veritas
This command should not return any actively running CloudPoint containers.
- (Optional) If you still see any active containers, repeat step 3. If that does not work, run the following command on each active container:
# docker kill container_name
For example:
# docker kill flexsnap-api
- After all the containers are stopped, take a snapshot of the volume on which you installed CloudPoint. Use the cloud provider's snapshot tools.
- After the snapshot completes, restart CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name: /full_path_to_volume_name -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version start
Here, version represents the currently installed CloudPoint product version.
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.0.1.5300 start
Note:
This is a single command. Ensure that you enter the command without any line breaks.
To backup CloudPoint when it is deployed on-premise
- Sign out of the CloudPoint user interface (UI).
- Stop CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name:/full_path_to_volume_name -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version stop
# sudo docker run -it --rm
Here, version represents the currently installed CloudPoint product version.
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.0.1.5300 stop
Note:
This is a single command. Ensure that you enter the command without any line breaks.
- Make sure that all CloudPoint containers are stopped. This step is important because all activity and connections to and from CloudPoint must be stopped to get a consistent CloudPoint backup.
Enter the following:
# docker ps | grep veritas
This command should not return any actively running CloudPoint containers.
- (Optional) If you still see any active containers, repeat step 3. If that does not work, run the following command on each active container:
# docker kill container_name
For example:
# docker kill flexsnap-api
- Back up the folder
/cloudpoint. Use any backup method you prefer.For example:
# tar -czvf cloudpoint_dr.tar.gz /cloudpoint
This command creates a compressed archive file named
cloudpoint_dr.tar.gzthat contains the data in the/cloudpointdirectory.