NetBackup™ Deployment Guide for Kubernetes Clusters

Perform the following steps to create EFS when upgrading NetBackup from version 10.0.0.1

1. To create EFS for primary server, see Create your Amazon EFS file system.

   EFS configuration can be as follow and user can update Throughput mode as required:

   Performance mode:  General Purpose

   Throughput mode: Provisioned (256 MiB/s)

   Availability zone: Regional

   Note:

   Throughput mode can be increased at runtime depending on the size of workloads and also if you are seeing performance issue you can increase the Throughput mode till 1024 MiB/s.

2. Install efs-csi-controller driver on EKS cluster.

   For more information on installing the driver, see Amazon EFS CSI driver.

3. Note down the EFS ID for further use.
4. Mount EFS on any EC-2 instance and create and create two directories on EFS to store NetBackup data.

   For more information, see Mount on EC-2 instance.

   For example,

   [root@sych09b03v30 ~]# mkdir /efs
   [root@sych09b03v30 ~]# mount -t nfs4 -o nfsvers=4.1,rsize=1048576,
   wsize=1048576,hard,timeo=600,retrans=2,noresvport
   <fs-0bde325bc5b8d6969>.efs.us-east-2.amazonaws.com:
   / /efs  # change EFS ID
   

(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