NetBackup™ Deployment Guide for Kubernetes Clusters

Upgrading Cloud Scale deployment

1. Patch file contains updated image names and tags. Operators are responsible for restarting the pods in correct sequence.

   Note the following:

   • Modify the patch file if your current environment CR specifies spec.primary.tag or spec.media.tag. The patch file listed below assumes the default deployment scenario where only spec.tag and spec.msdpScaleouts.tag are listed.

   • When upgrading from embedded Postgres to containerized Postgres add dbSecretName to the patch file.

   • If the images for the new release that you are upgrading to are in a different container registry, modify the patch file to change the container registry.

   • In case of Cloud Scale upgrade, if the capacity of the primary server log volume is greater than the default value, you need to modify the primary server log volume capacity (spec.primary.storage.log.capacity) to default value that is, 30Gi . After upgrading to version 10.5 or later, the decoupled services log volume should use the default log volume, while the primary pod log volume will continue to use the previous log size.

   Examples of .json files:

   • For containerized_cloudscale_patch.json upgrade from 10.4 or later:

     [
       {
         "op" : "replace" ,
         "path" : "/spec/tag" ,
         "value" : "10.5-xxxx"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/msdpScaleouts/0/tag" ,
         "value" : "20.5-0027"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/cpServer/0/tag" ,
         "value" : "10.5.x.x-xxxx"
       }
     ]

   • For containerized_cloudscale_patch.json with primary and , media tags but no global tag:

     [
       {
         "op": "replace",
         "path": "/spec/dbSecretName",
         "value": "dbsecret"
       }, 
       {
         "op" : "replace" ,
         "path" : "/spec/primary/tag" ,
         "value" : "10.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/mediaServers/0/tag" ,
         "value" : "10.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/msdpScaleouts/0/tag" ,
         "value" : "20.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/cpServer/0/tag" ,
         "value" : "10.5.x.xxxxx"
       }
     ]

   • For DBAAS_cloudscale_patch.json:

     Note:

     This patch file is to be used only during DBaaS to DBaaS migration.

     [
       {
         "op" : "replace" ,
         "path" : "/spec/dbSecretProviderClass" ,
         "value" : "dbsecret-spc"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/tag" ,
         "value" : "10.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/msdpScaleouts/0/tag" ,
         "value" : "20.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/cpServer/0/tag" ,
         "value" : "10.5.x.xxxxx"
       }
     ]

   • For Containerized_cloudscale_patch.json with new container registry:

     Note:

     If the images for the latest release that you are upgrading to are in a different container registry, modify the patch file to change the container registry.

     [
       {
         "op" : "replace" ,
         "path" : "/spec/dbSecretName" ,
         "value" : "dbsecret"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/tag" ,
         "value" : "10.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/msdpScaleouts/0/tag" ,
         "value" : "20.5"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/cpServer/0/tag" ,
         "value" : "10.5.x.xxxxx"
       }
       {
         "op" : "replace" ,
         "path" : "/spec/containerRegistry" ,
         "value" : "newacr.azurecr.io"
       },
       {
         "op" : "replace" ,
         "path" : "/spec/cpServer/0/containerRegistry" ,
         "value" : "newacr.azurecr.io"
       } 
     ]

2. Use the following command to obtain the environment name:

   $ kubectl get environments -n netbackup

3. Navigate to the directory containing the patch file and upgrade the Cloud Scale deployment as follows:

   $ cd scripts/

   $ kubectl patch environment <env-name> --type json -n netbackup --patch-file cloudscale_patch.json

4. Wait until Environment CR displays the status as ready. During this time pods are expected to restart and any new services to start. Operators are responsible for restarting the pods in the correct sequence.

   The status of the upgrade for Primary, Msdp, Media and CpServer are displayed as follows:

   /VRTSk8s-netbackup-<version>/scripts$ kubectl get environment -n netbackup
   NAME          READY   AGE   STATUS
   env-testupg   3/4     28h   Upgrading Primary 
   

   VRTSk8s-netbackup-<version>/scripts$ kubectl get environment -n netbackup
   NAME          READY   AGE   STATUS
   env-testupg   3/4     28h   Upgrading Msdp

   VRTSk8s-netbackup-<version>/scripts$ kubectl get environment -n netbackup
   NAME          READY   AGE   STATUS
   env-testupg   3/4     28h   Upgrading Media

   VRTSk8s-netbackup-<version>/scripts$ kubectl get environment -n netbackup
   NAME          READY   AGE   STATUS
   env-testupg   3/4     28h   Upgrading CpServer

5. Log into the primary server and use the following command to resume the backup job processing by using the following commands:

   kubectl exec -it pod/,primary-podname> -n netbackup -- bash

   # nbpemreq -resume_scheduling