Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- About the deployment approach
 - Deciding where to run CloudPoint
 - About deploying CloudPoint in the cloud
 - 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 using the Docker image
 - CloudPoint cloud plug-ins
 - CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
 - Nutanix Files plug-in configuration notes
 - Dell EMC Unity array plug-in configuration parameters
 - Pure Storage FlashArray plug-in configuration notes
 - HPE RMC plug-in configuration notes
 - Hitachi plug-in configuration notes
 - InfiniBox plug-in configuration notes
 - How to configure the CloudPoint storage array plug-ins?
 
 - CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
 - Oracle plug-in configuration notes
 - MongoDB plug-in configuration notes
 - About the installation and configuration process
 - Preparing to install the Linux-based agent
 - Preparing to install the Windows-based agent
 - Downloading and installing the CloudPoint agent
 - Registering the Linux-based agent
 - Registering the Windows-based agent
 - Configuring the CloudPoint application plug-in
 - Configuring VSS to store shadow copies on the originating drive
 - Creating a NetBackup protection plan for cloud assets
 - Subscribing cloud assets to a NetBackup protection plan
 - About snapshot restore
 - Restore requirements and limitations for Microsoft SQL Server
 - Restore requirements and limitations for Oracle
 - Restore requirements and limitations for MongoDB
 - Steps required before restoring SQL AG databases
 - Recovering a SQL database to the same location
 - Recovering a SQL database to an alternate location
 - Additional steps required after a SQL Server snapshot restore
 - Additional steps required after restoring SQL AG databases
 - SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
 - Disk-level snapshot restore fails if the original disk is detached from the instance
 - Additional steps required after a MongoDB snapshot restore
 - Additional steps required after an Oracle snapshot restore
 - Additional steps required after restoring an AWS RDS database instance
 
 - Protecting assets with CloudPoint's agentless feature
 
 - Preparing for CloudPoint installation
 - Section II. CloudPoint maintenance
 
Restoring CloudPoint
You can restore CloudPoint using any of the following methods:
Recover CloudPoint using a snapshot you have in the cloud
Recover CloudPoint using a backup located on-premises
To recover CloudPoint using a snapshot you have in the cloud
- Using your cloud provider's dashboard or console, create a volume from the existing snapshot.
 - Create a new virtual machine with specifics equal to or better than your previous CloudPoint server.
 - Install Docker on the new server.
 - Attach the newly-created volume to this CloudPoint server instance.
 - Create the CloudPoint  installation directory on this server.
Use the following command:
# mkdir /full_path_to_cloudpoint_installation_directory
For example:
# mkdir /cloudpoint
 - Mount the attached volume to the installation directory you just created.
Use the following command:
# mount /dev/device-name /full_path_to_cloudpoint_installation_directory
For example:
# mount /dev/xvdb /cloudpoint
 -  Verify that all CloudPoint related configuration data and files are in the directory.
Enter the following command:
# ls -l /cloudpoint
 - Download or copy the CloudPoint installer binary to the new server.
 -  Install CloudPoint. 
Use the following command:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:8.3.1.5300 install
Here,
8.3.1.5300represents the CloudPoint version. Replace it as per your currently installed product version.Note:
This is a single command. Ensure that you enter the command without any line breaks.
The installation program detects an existing version of CloudPoint and re-installs all CloudPoint services without overwriting existing content.
Messages similar to the following are displayed on the command prompt:
Configuration started at time Wed May 13 22:20:47 UTC 2020 This is a re-install. Checking if a 1.0 release container exists ...
Note the line that indicates that the operation is a re-install.
 - When the installation completes, you can resume working with CloudPoint using your existing credentials.
 
To recover CloudPoint using a backup located on-premise
- Copy the existing CloudPoint backup to the new CloudPoint server and extract it to the CloudPoint installation directory.
In the following example, because
/cloudpointwas backed up, the command creates a new/cloudpointdirectory.# tar -zxf cloudpoint_dr.tar.gz -C /cloudpoint/
 - Download or copy the CloudPoint installer binary to the new server.
 -  Install CloudPoint.
Use the following command:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:8.3.1.5300 install
Here,
8.3.1.5300represents the CloudPoint version. Replace it as per your currently installed product version.Note:
This is a single command. Ensure that you enter the command without any line breaks.
The installation program detects an existing version of CloudPoint and re-installs all CloudPoint services without overwriting existing content.
Messages similar to the following are displayed on the command prompt:
Configuration started at time Wed May 13 22:20:47 UTC 2020 This is a re-install. Checking if a 1.0 release container exists ...
Note the line that indicates that the operation is a re-install.
 - When the installation completes, you can resume working with CloudPoint using your existing credentials.
 
More Information