Upgrading NetBackup application
Ensure that all the steps mentioned in the following section are performed before performing the upgrade of NetBackup application:
See Preparing for NetBackup upgrade.
Ensure that the following server upgrade sequence is followed:
Primary server: Upgrade and verify it is successfully upgraded
MSDP server: Upgrade and verify it is successfully upgraded
Media server: Upgrade and verify it is successfully upgraded
Note the following:
All the media server replicas would be upgraded and media server autoscaler would scale in the media server replicas to .
Default value of is 1 and if it is not changed then after upgrade media servers would be scaled in to 1.
It is recommended to use a separate node pool for media pods. Cluster autoscaling must be enabled on media server node pool. See Config-Checker utility.
To upgrade the primary server and media server, edit the current environment using the following command:
kubectl edit environment -n <netbackup namespace>
Update the with new image tag in section.
Update the with new image tag in section.
Update the for catalog volume for primary server in Storage subsection of primary section in environment.yaml file.
(AKS-specific) Update the details of data volume for primary server in environment.yaml file. Storage class must be of Azure managed disk storage type.
Save the changes to the environment and exit.
Primary server and media server pods would start with new container images respectively.
Note:
Upgrade the PrimaryServer first and then change the tag for MediaServer by re-editing the environment to upgrade the MediaServer also. If this sequence is not followed then deployment may go into inconsistent state
Perform the following if upgrade fails in between for primary server or media server
- Check the installation logs using the following command:
kubectl logs <PrimaryServer-pod-name/MediaServer-pod-name> -n <PrimaryServer/MediaServer-CR-namespace>
- If required, check the NetBackup logs by performing exec into the pod using the following command:
kubectl exec -it -n <PrimaryServer/MediaServer-CR-namespace> <PrimaryServer/MediaServer-pod-name> -- bash
- Fix the issue and restart the pod by deleting the respective pod with the following command:
kubectl delete < PrimaryServer/MediaServer-pod-name > -n <PrimaryServer/MediaServer-CR-namespace>
- New pod would be created and upgrade process will be restarted for the respective NetBackup server.
- Data migration jobs create the pods that run before deployment of primary server. Data migration pod exist after migration for one hour only if data migration job failed. The logs for data migration execution can be checked using the following command:
kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>
User can copy the logs to retain them even after job pod deletion using the following command:
kubectl logs <migration-pod-name> -n <netbackup-environment-namespace> > jobpod.log
Note:
Downgrade of NetBackup servers is not supported. If this is done, there are chances of inconsistent state of NetBackup deployment.