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
- Downloading the CloudPoint extension
- 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 (AKS) in Azure
- Preparing to install the extension on a managed Kubernetes cluster (EKS) in AWS
- Install extension using the Kustomize and CR YAMLs
- Installing the CloudPoint extension on Azure (AKS)
- Installing the CloudPoint extension on AWS (EKS)
- 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
- FUJITSU AF/DX plug-in configuration notes
- NetApp NAS plug-in configuration notes
- Dell EMC PowerStore plug-in configuration notes
- Dell EMC PowerStore NAS plug-in configuration notes
- Dell EMC PowerFlex plug-in configuration notes
- Dell EMC XtremIO SAN plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- Pure Storage FlashBlade plug-in configuration notes
- IBM Storwize 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
- 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
- Restore requirements and limitations for Microsoft SQL Server
- Restore requirements and limitations for Oracle
- Additional steps required after an Oracle 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
Upgrade in Podman environment
To upgrade CloudPoint server in Podman environment
- Download the CloudPoint upgrade installer.
On the CloudPoint download page, click Download Now to download the CloudPoint installer.
The CloudPoint software components are available in the form of images which are packaged in a compressed file. The file name has the following format:
Veritas_CloudPoint_9.x.x.x.x.tar.gz
Example: Veritas_CloudPoint_9.1.0.0.9349.tar.gz
- Copy the downloaded compressed image file to the computer on which you want to deploy CloudPoint.
- 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.tarThe output resembles the following:
flexsnap-cloudpoint-9.x.x.x.x.img flexsnap-coordinator-9.x.x.x.x.img flexsnap-agent-9.x.x.x.x.img flexsnap-onhostagent-9.x.x.x.x.img flexsnap-policy-9.x.x.x.x.img flexsnap-scheduler-9.x.x.x.x.img flexsnap-config-9.x.x.x.x.img flexsnap-certauth-9.x.x.x.x.img flexsnap-rabbitmq-9.x.x.x.x.img flexsnap-api-gateway-9.x.x.x.x.img flexsnap-notification-9.x.x.x.x.img flexsnap-fluentd-9.x.x.x.x.img flexsnap-nginx-9.x.x.x.x.img flexsnap-idm-9.x.x.x.x.img flexsnap-workflow-9.x.x.x.x.img flexsnap-listener-9.x.x.x.x.img flexsnap-datamover-9.x.x.x.x.img flexsnap-mongodb-9.x.x.x.x.img flexsnap-podman-api.service flexsnap-podman-containers.service flexsnap_preinstall.sh dnsname
- Run the following command to prepare the CloudPoint host for installation:
# ./flexsnap_preinstall.sh
The output resembles the following:
Executing the following changes on this node to prepare the CloudPoint server for installation: 1) Loading CloudPoint service images. 2) Copying dnsname plugin to the /usr/libexec/cni folder. 3) Check if dnsmasq rpm is installed on the host, if not, installation is done automatically. 4) Creating and starting the systemd service for the Podman API server. Do you want to continue? (Yes/No): Yes Loaded image(s): localhost/veritas/flexsnap-agent:9.1.0.0.9349 Loaded image(s): localhost/veritas/flexsnap-api-gateway:9.1.0.0.9349 Loaded image(s): localhost/veritas/flexsnap-certauth:9.1.0.0.9349 ............ ............ Loaded image(s): localhost/veritas/flexsnap-workflow:9.1.0.0.9349 Copying dnsname plugin...done Starting Podman API service...done
Note:
The output is truncated to fit the page.
- Verify that there are no protection policy snapshots or other operations in progress and then stop 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:<current_version> stopHere, current_version represents the currently installed CloudPoint version, for example '9.0.0.0.9234'
Note:
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-workflow-system-0-0 ...done Stopping container: flexsnap-workflow-indexing-0-0 ...done Stopping container: flexsnap-workflow-general-0-0 ...done Stopping container: flexsnap-listener ...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.
- 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.
The output resembles the following:
Installing the services Configuration started at time: Mon May 3 11:57:33 UTC 2021 podman server version: 2.0.5 Supported: true This is an upgrade to NetBackup CloudPoint 9.1.0.0.9349 Previous CloudPoint version: 9.0.0.0.9234 Do you want to take a backup of the CloudPoint metadata prior to upgrade? (y/n): y Taking backup of CloudPoint metadata...done Backup completed successfully. Backup file located at /cloudpoint/backup/cloudpoint_9.0.0.0.9234.tar.gz. [Storing /cloudpoint/keys/idm_store] [Storing /cloudpoint/keys/flexsnap-idm_store] Creating network: flexsnap-network ...done Starting container: flexsnap-fluentd ...done Starting container: flexsnap-mongodb ...done Starting container: flexsnap-rabbitmq ...done Starting container: flexsnap-certauth ...done Starting container: flexsnap-api-gateway ...done Starting container: flexsnap-coordinator ...done Starting container: flexsnap-listener ...done Starting container: flexsnap-agent ...done Starting container: flexsnap-onhostagent ...done Starting container: flexsnap-scheduler ...done Starting container: flexsnap-policy ...done Starting container: flexsnap-notification ...done Starting container: flexsnap-idm ...done Starting container: flexsnap-config ...done Starting container: flexsnap-nginx ...done Upgrade finished at time: Mon May 3 11:58:51 UTC 2021 Before using backups from cloud snapshots, re-register CloudPoint with the NetBackup primary server
- (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 upgrade process. 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.