To upgrade CloudPoint in Docker environment

1. Download the CloudPoint upgrade installer.

   Example: Veritas_CloudPoint_10.0.0.9818.img.gz

2. Unzip and un-tar the image file and list the contents:

   # gunzip VRTScloudpoint-podman-10.0.0.9818.tar.gz

   # tar -xvf VRTScloudpoint-podman-10.0.0.9818.tar

3. Run the following command to prepare the CloudPoint host for installation:

   # ./flexsnap_preinstall.sh

4. 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> install

   For 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 -y

   Here, new_version represents the CloudPoint version you are upgrading to, for example 10.0.0.9818

   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.

5. (Optional) Run the following command to remove the previous version images.

   # podman rmi -f <imagename>:<oldimage_tagid>

6. To verify that the new CloudPoint version is installed successfully:

   See Verifying that CloudPoint is installed successfully.

To migrate CloudPoint in Podman environment

1. 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> stop

   Here, 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.1.0.0.9349 stop

   Note:

   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.

2. Migrate the CloudPoint configuration data to the RHEL 8.5 or 8.4 host:

   • If you have upgraded from RHEL 7.x to RHEL 8.5 or 8.4, copy the /cloudpoint mountpoint data from RHEL 7.x system and move it to the RHEL8.5 or 8.4 system under /cloudpoint folder.

   • If you have created a new system with RHEL 8.5 or 8.4:

     • 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.5 or 8.4 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 migration, install the new_version on the new host by following the steps mentioned in the To upgrade CloudPoint in Docker environment.

3. During migration process, if CloudPoint server is migrated to another system or IP address is changed, then regenerate the certificates as follows:

   • Stop the CloudPoint services using the following command:

     [root@ip-172-31-24-178 ec2-user]# podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-cloudpoint:10.0.0.9818 stop

   • Regenerate the certificates using the following command:

     # podman run -it --rm -v /cloudpoint:/cloudpoint --entrypoint "/cloudpoint/scripts/cp_regenerate_certs.sh" veritas/flexsnap-cloudpoint:10.0.0.9818 -i <CP_IP_ADDRESS> -h <CP_HOSTNAME>

     Setting up certificate authority ...done
     Generating certificates for servers ...done
     Generating certificates for clients ...done
     Adding MongoDB and RabbitMQ certificate to the trust store ...[Storing /cloudpoint/keys/idm_store]
     [Storing /cloudpoint/keys/flexsnap-idm_store]
     done
     Creating symlinks for nginx certificates ...done

   • Start the CloudPoint services using the following command:

     [root@ip-172-31-24-178 ec2-user]# podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-cloudpoint:10.0.0.9818 start

4. Depending on the following appropriate scenario, update the /cloudpoint/openv/netbackup/bp.conf file to update the value of CLIENT_NAME to new CloudPoint IP/hostname.

   • If IP address doe not change, then edit the CloudPoint server entry and provide reissue token.

   • If IP address changes, disable previous CloudPoint host, and add CloudPoint server with new IP. And then edit the entry with reissue token.

5. After migrating CloudPoint to a RHEL 8.5 or 8.4 host, perform the following steps to upgrade CloudPoint to 10.0.

   Refer to the detailed procedure "To upgrade CloudPoint server in Podman environment".

   See Upgrading CloudPoint.

6. This concludes the migration and upgrade process for CloudPoint. Verify that your CloudPoint configuration settings and data are preserved as is.
7. 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.