NetBackup™ Deployment Guide for Kubernetes Clusters

(AKS-specific) Perform the following steps when upgrading NetBackup from version 10.2 or lower on AKS cluster version 1.25

1. Pause the primary and media server spec by setting the value as paused: true in primaryServer and mediaServer sections in environment CR using the following command:

   Kubectl edit environments -n <namespace>

2. Change the value of primary and server statefulset to 0 using the following command:

   kubectl scale statefulsets <stateful-set-name> --replicas=0 -n <namespace>

3. Change the value of media server statefulset to 0 using the following command:

   kubectl scale statefulsets <stateful-set-name> --replicas=0 -n <namespace>

4. Delete the revertfix yaml file using the following command:

   kubectl delete -f <revertfix_yaml>

5. Restart the AKS cluster or set the scale node to 0 and rescale it.
6. Upgrade to the latest versions of NetBackup and MSDP operator.
7. Un pause the primary and media server spec by changing the value as paused: falsein primaryServer and mediaServer sections in environment CR using the following command:

   kubectl edit environments -n <namespace>

8. Change the imageTag to the latest imageTag for primary and media servers together and save it.

(EKS-specific) Perform the following steps when upgrading NetBackup from version 10.1

1. Make primary environment controller paused to true as follows:

   • Edit the environment custom resource using the kubectl edit Environment <environmentCR_name> -n <namespace> command.

   • To pause the reconciler of the particular custom resource, change the paused: false value to paused: true in the primaryServer or mediaServer section and save the changes.

   • Scale down the primary server using the following commands:

     • To get statefulset name: kubectl get sts -n <namespace>

     • To scale down the STS: kubectl scale sts --replicas=0 < STS name of primary server> -n <Namespace>

2. Upgrade the MSDP with new build and image tag. Apply the following command to MSDP:

   ./kubectl-msdp init --image <Image name:Tag> --storageclass <Storage Class Name> --namespace <Namespace>

3. Edit the sample/environment.yaml file from new build and perform the following changes:

   • Add the tag: <new_tag_of_upgrade_image> tag separately under primary sections.

   • Provide the EFS ID for storageClassName of catalog volume in primary section.

     Note:

     The provided EFS ID for storageClassName of catalog volume must be same as previously used EFS ID to create PV and PVC.

     • Use the following command to retrieve the previously used EFS ID from PV and PVC:

       kubectl get pvc -n <namespace>

       From the output, copy the name of catalog PVC which is of the following format:

       catalog-<resource name prefix>-primary-0

     • Describe catalog PVC using the following command:

       kubectl describe pvc <pvc name> -n <namespace>

       Note down the value of Volume field from the output.

     • Describe PV using the following command:

       kubectl describe pv <value of Volume obtained from above step>

       Note down the value of VolumeHandle field from the output which is the previously used EFS ID.

   • For data and logs volume, provide the storageClassNameand then apply environment.yaml file using the following command and ensure that the primary server is upgraded successfully:

     kubectl apply -f environment.yaml

     • Upgrade the MSDP Scaleout by updating the new image tag in msdpscaleout section in environment.yaml file.

     • Apply environment.yaml file using the following command and ensure that MSDP is deployed successfully:

       kubectl apply -f environment.yaml

     • Edit the environment.yaml file and update the image tag for Media Server in mediaServer section.

     • Apply environment.yaml file using the following command and ensure that the Media Server is deployed successfully:

       kubectl apply -f environment.yaml