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
- CloudPoint extension sizing recommendations
- Creating an instance or preparing the host to install CloudPoint
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- Preparing CloudPoint for backup from snapshot jobs
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Before you begin installing CloudPoint extensions
- Preparing to install the extension on a VM
- Installing the CloudPoint extension on a VM
- Preparing to install the extension on a managed Kubernetes cluster
- Downloading the CloudPoint extension
- Installing the CloudPoint extension on a managed Kubernetes cluster
- Managing the extensions
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- How to configure the CloudPoint storage array plug-ins?
- NetApp plug-in configuration notes
- ACL configuration on NetApp array
- Nutanix Files plug-in configuration notes
- Configuring ACL for Nutanix array
- Dell EMC Unity array plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- HPE RMC plug-in configuration notes
- HPE XP plug-in configuration notes
- Hitachi plug-in configuration notes
- Hitachi (HDS VSP 5000) plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Dell EMC PowerMax and VMax plug-in configuration notes
- Qumulo plug-in configuration notes
- 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
- Additional steps required after an Oracle snapshot restore
- Restore requirements and limitations for MongoDB
- Additional steps required after a MongoDB snapshot restore
- 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 restoring an AWS RDS database instance
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup CloudPoint
- CloudPoint security
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Preparing to uninstall CloudPoint
- Backing up CloudPoint
- Unconfiguring CloudPoint plug-ins
- Unconfiguring CloudPoint agents
- Removing the CloudPoint agents
- Removing CloudPoint from a standalone Docker host environment
- Removing CloudPoint extensions - VM-based or managed Kubernetes cluster-based
- Restoring CloudPoint
- Troubleshooting CloudPoint
Migrate and upgrade CloudPoint on RHEL 8.3
Perform the following steps to migrate CloudPoint 8.3 or 9.0 from your RHEL 7.x host to the new RHEL 8.3 host.
To migrate CloudPoint
- On the RHEL 7.x host, verify that there are no protection policy snapshots or other operations in progress and then stop CloudPoint by running the following command:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:<current_version> stopHere, current_version represents the currently installed CloudPoint version.
Example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:9.0.0.0.9234 stopNote:
This is a single command. Ensure that you enter the command without any line breaks.
The CloudPoint containers are stopped one by one. Messages similar to the following appear on the command line:
Stopping the services Stopping container: flexsnap-agent.8a51aac1848c404ab61e4625d7b88703 ...done Stopping container: flexsnap-workflow-long-15 ...done Stopping container: flexsnap-workflow-long-14 ...done Stopping container: flexsnap-workflow-long-13 ...done Stopping container: flexsnap-workflow-long-12 ...done Stopping container: flexsnap-workflow-long-11 ...done Stopping container: flexsnap-workflow-long-10 ...done Stopping container: flexsnap-workflow-long-9 ...done Stopping container: flexsnap-workflow-long-8 ...done Stopping container: flexsnap-workflow-long-7 ...done Stopping container: flexsnap-workflow-long-6 ...done Stopping container: flexsnap-workflow-long-5 ...done Stopping container: flexsnap-workflow-long-4 ...done Stopping container: flexsnap-workflow-long-3 ...done Stopping container: flexsnap-workflow-long-2 ...done Stopping container: flexsnap-workflow-long-1 ...done Stopping container: flexsnap-workflow-long-0 ...done Stopping container: flexsnap-workflow-15 ...done Stopping container: flexsnap-workflow-14 ...done Stopping container: flexsnap-workflow-13 ...done Stopping container: flexsnap-workflow-12 ...done Stopping container: flexsnap-workflow-11 ...done Stopping container: flexsnap-workflow-10 ...done Stopping container: flexsnap-workflow-9 ...done Stopping container: flexsnap-workflow-8 ...done Stopping container: flexsnap-workflow-7 ...done Stopping container: flexsnap-workflow-6 ...done Stopping container: flexsnap-workflow-5 ...done Stopping container: flexsnap-workflow-4 ...done Stopping container: flexsnap-workflow-3 ...done Stopping container: flexsnap-workflow-2 ...done Stopping container: flexsnap-workflow-1 ...done Stopping container: flexsnap-workflow-0 ...done Stopping container: flexsnap-nginx ...done Stopping container: flexsnap-notification ...done Stopping container: flexsnap-policy ...done Stopping container: flexsnap-scheduler ...done Stopping container: flexsnap-idm ...done Stopping container: flexsnap-onhostagent ...done Stopping container: flexsnap-agent ...done Stopping container: flexsnap-coordinator ...done Stopping container: flexsnap-api-gateway ...done Stopping container: flexsnap-certauth ...done Stopping container: flexsnap-rabbitmq ...done Stopping container: flexsnap-mongodb ...done Stopping container: flexsnap-fluentd ...done
Wait for all the CloudPoint containers to be stopped and then proceed to the next step.
- Migrate the CloudPoint configuration data to the RHEL 8.3 host:
If you have upgraded from RHEL 7.x to RHEL 8.3, copy the /cloudpoint mountpoint data from RHEL 7.x system and move it to the RHEL8.3 system under /cloudpoint folder.
If you have created a new system with RHEL 8.3:
Run the following command to unmount /cloudpoint from the current host.
# umount /cloudpoint
Detach the data disk that was mounted on /cloudpoint mountpoint.
Note:
For detailed instructions to detach or attach the data disks, follow the documentation provided by your cloud or storage vendor.
On the RHEL8.3 host, run the following commands to create and mount the disk:
# mkdir /cloudpoint
# mount /dev/<diskname> /cloudpoint
For vendor-specific details
See Creating and mounting a volume to store CloudPoint data.
This concludes the CloudPoint migration process.
- After migrating CloudPoint to a RHEL 8.3 host, perform the following steps to upgrade CloudPoint to 9.1
Refer to the detailed procedure "To upgrade CloudPoint server in Podman environment".
See Upgrading CloudPoint.
Brief steps to upgrade CloudPoint in Podman environment
- Download the CloudPoint upgrade installer.
Example: Veritas_CloudPoint_9.1.0.0.9349.img.gz
- Unzip and un-tar the image file and list the contents:
# gunzip
VRTScloudpoint-podman-9.1.0.0.9349.tar.gz# tar -xvf
VRTScloudpoint-podman-9.1.0.0.9349.tar - Run the following command to prepare the CloudPoint host for installation:
# ./flexsnap_preinstall.sh
- Upgrade CloudPoint by running the following command:
# podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-cloudpoint:<new_version> installFor an unattended installation, use the following command:
# podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-cloudpoint:<new_version> install -yHere, new_version represents the CloudPoint version you are upgrading to, for example '9.1.0.0.9349'
The -y option passes an approval for all the subsequent installation prompts and allows the installer to proceed in a non-interactive mode.
Note:
Ensure that you enter the command without any line breaks.
The installer first loads the individual service images and then launches them in their respective containers.
- (Optional) Run the following command to remove the previous version images.
# podman rmi -f <imagename>:<oldimage_tagid>
- To verify that the new CloudPoint version is installed successfully:
- This concludes the migration and upgrade process for CloudPoint. Verify that your CloudPoint configuration settings and data are preserved as is.
- If CloudPoint is not registered with the NetBackup primary server, you must register it now.
Refer to the NetBackup Web UI Cloud Administrator's Guide for instructions.