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
- 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 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
- Working with your CloudPoint license
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Installing CloudPoint
The following figure shows where you are at in the CloudPoint installation and configuration process.
Before you complete the steps in this section, make sure that you complete the following:
Decide where to install CloudPoint.
Note:
If you plan to install CloudPoint on multiple hosts, read this section carefully and understand the implications of this approach.
Ensure that your environment meets system requirements.
Create the instance on which you install CloudPoint or prepare the physical host.
See Creating an instance or preparing the physical host to install CloudPoint.
Install Docker.
See Installing Docker.
Create and mount a volume to store CloudPoint data.
See Creating and mounting a volume to store CloudPoint data.
Verify that specific ports are open on the instance or physical host.
If you want to install or upgrade CloudPoint in an unattended mode, ensure that you use the appropriate command syntax.
If you want to install CloudPoint on a host where the root file system (
rootfsor/shared subtree) is not mounted in asharedmode, ensure that you use the appropriate command syntax.Although CloudPoint supports installation in such an environment, certain restrictions apply.
See CloudPoint installation fails if rootfs is not mounted in a shared mode.
Note:
When you deploy CloudPoint, you may want to copy the commands below and paste them in your command line interface. If you do, replace the information in these examples that is different from your own: the product and build version, the download directory path, and so on.
To deploy CloudPoint
- Download the CloudPoint image.
You can use the free edition or purchase a licensed version. Refer to the following for more information:
https://www.veritas.com/product/backup-and-recovery/cloudpoint/buy
The CloudPoint image name has the following format:
Veritas_CloudPoint_2.x.x_IE.img.gz - (Optional) If necessary, copy the downloaded image to the system on which you want to deploy CloudPoint.
- Change directories to where you have downloaded the CloudPoint image.
- Type the following command to load the image into Docker:
# sudo docker load -i Veritas_CloudPoint_2.x.x_IE.img.gz
For example:
# sudo docker load -i Veritas_CloudPoint_2.0.2_IE.img.gz
Messages similar to the following appear on the command line:
788ce2310e2f: Loading layer [============>] 126.8 MB/126.8 MB aa4e47c45116: Loading layer [============>] 15.87 kB/15.87 kB b3968bc26fbd: Loading layer [============>] 14.85 kB/14.85 kB c9748fbf541d: Loading layer [============>] 5.632 kB/5.632 kB 2f5b0990636a: Loading layer [============>] 3.072 kB/3.072 kB d1348a46025a: Loading layer [============>] 214.2 MB/214.2 MB de54ad3327fe: Loading layer [============>] 12.06 MB/12.06 MB a8f411dfb821: Loading layer [============>] 1.35 GB/1.35 GB dc3db1bf7ffd: Loading layer [============>] 25.6 kB/25.6 kB e2344be00294: Loading layer [============>] 25.6 kB/25.6 kB Loaded image: veritas/flexsnap-cloudpoint:2.0.2.5300
Make a note of the loaded image name and version that appears on the last line of the output. The version represents the CloudPoint product version that is being installed. You will specify these details in the next step.
- Type the following command to run the CloudPoint container:
# 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> install
If the CloudPoint host is behind a proxy server, use the following command instead:
# sudo docker run -it --rm -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -e VX_HTTP_PROXY=<http_proxy_value> -e VX_HTTPS_PROXY=<https_proxy_value> -e VX_NO_PROXY=<no_proxy_value> -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:<version> install
Replace the following parameters as per your environment:
Parameter
Description
<full_path_to_volume_name>
Represents the path to the CloudPoint data volume, which typically is
/cloudpoint.<version>
Represents the CloudPoint product version that you noted in the earlier step.
<http_proxy_value>
(required only if the instance uses a proxy server)
Represents the value to be used as the HTTP proxy for all connections.
For example,
"http://proxy.mycompany.com:8080/".<https_proxy_value>
(required only if the instance uses a proxy server)
Represents the value to be used as the HTTPS proxy for all connections.
For example,
"https://proxy.mycompany.com:8080/".<no_proxy_value>
(required only if the instance uses a proxy server)
Represents the addresses that are allowed to bypass the proxy server. You can specify host names, IP addresses, and domain names in this parameter.
Use commas to separate multiple entries. For example,
"localhost,mycompany.com,192.168.0.10:80".Note:
If CloudPoint is being deployed in the cloud, ensure that you set the following values in this parameter:
For an AWS instance, add the following:
169.254.169.254
For a GCP virtual machine, add the following:
169.254.169.254,metadata,metadata.google.internal
For an Azure virtual machine, add the following:
169.254.169.254
CloudPoint uses these addresses to gather instance metadata from the instance metadata service.
For example, if the CloudPoint version is
2.0.2.5300, the command syntax is as follows:# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.0.2.5300 install
If using a proxy server, then using the examples provided in the table earlier, the command syntax is as follows:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -e VX_HTTP_PROXY="http://proxy.mycompany.com:8080/" -e VX_HTTPS_PROXY="https://proxy.mycompany.com:8080/" -e VX_NO_PROXY="localhost,mycompany.com,192.168.0.10:80" -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.0.2.5300 install
Note:
This is a single command. Ensure that you enter the command without any line breaks.
In this step, CloudPoint does the following:
Creates containers for each of the CloudPoint services.
Runs the flexsnap-api container.
Creates self-signed keys and certificates for nginx.
Runs the flexsnap-cloudpointconsole container.
When these operations are completed, CloudPoint displays the following in the command prompt:
Please go to the UI and configure CloudPoint now. Waiting for CloudPoint configuration to complete ............
If you have difficulty with this step, note the following:
If you do not specify the volume as -v full_path_to_volume_name:/full_path_to_volume_name, the container writes to the Docker host file system.
If Docker fails to start, it may be because there is not enough space available for MongoDB.
- This concludes the CloudPoint deployment process. The next step is to launch the CloudPoint user interface in your browser and complete the final configuration steps.
See Configuring CloudPoint from your browser and signing in.
Note:
If you ever need to restart CloudPoint, use the docker run command so that your environmental data is preserved.