Preparing to upgrade CloudPoint
Note the following before you upgrade
Ensure that the CloudPoint instance, virtual machine, or physical host meets the requirements of the CloudPoint version 9.1.
When you upgrade CloudPoint, all the snapshot data and configuration data from your previous version is maintained in the external
/cloudpointdata volume. This information is external to the CloudPoint container and the image and is preserved during the upgrade.However, you can take a backup of all the data in the
/cloudpointvolume during the upgrade process when prompted or manually, if required.Ensure that no jobs are running on CloudPoint.
If you are using NetBackup Web UI, disable the CloudPoint server and wait for all the in-progress jobs to complete. Use the nbstlutil command to cancel all the pending SLP operations. Use one of the following commands:
To cancel the pending SLP operation for a specific image, use nbstlutil cancel -backupid <value>
To cancel the pending SLP operation for images that belong to specific lifecycle, use nbstlutil cancel -lifecycle <name>
If you are using NetBackup Administration console (Java UI), on the NetBackup primary server, run the following command to stop all NetBackup processes:
UNIX: /usr/openv/netbackup/bin/bp.kill_all
Windows: install_path\NetBackup\bin\bpdown -f
After you upgrade CloudPoint, if required you can upgrade the NetBackup primary server. Also, you must enable the CloudPoint server from NetBackup Web UI.
After upgrading, all the CloudPoint servers that you want to use for backup from snapshot or restore from backup jobs, must be re-edited by providing a token so that NetBackup certificates are generated in the CloudPoint server. See Edit a CloudPoint server section, in the NetBackup Web UI Cloud Administrator's Guide.