NetBackup™ Deployment Guide for Kubernetes Clusters

EEB installation

1. Download the EEB package to access the host.
2. Extract and load the docker images from the installation tar file on the access host using the following command:

   tar -xvf <build_tar_file>

   flexsnap_preinstall.sh

3. Create image tags to map the source image with the target image, so that the images can be pushed to the AWS/Azure container registry.

   To tag the images, run the following command for each image depending on the container platform running on your host:

   • For Docker: # docker tag source_image_name:tag container_registry_name/target_image_name:tag

   • For Podman: # podman tag source_image_name:tag container_registry_name/target_image_name:tag

   For example,

   source_image_name = veritas/flexsnap-deploy
   source_image_tag = 10.3.0.0.1041  (SnapshotManager_EEB_version)
   target_image_name = veritas/flexsnap-deploy
   target_image_tag = 10.3.0.0.1041  (SnapshotManager_EEB_version)
   container_registry_name = cpautomation.azurecr.io

   docker tag veritas/flexsnap-deploy:10.3.0.0.1041 cpautomation.azurecr.io/veritas/flexsnap-deploy:10.3.0.0.1041

   Images for 10.3 are:

   veritas/flexsnap-core
   veritas/flexsnap-deploy
   veritas/flexsnap-nginx
   veritas/flexsnap-fluentd
   veritas/flexsnap-rabbitmq
   veritas/flexsnap-postgresql
   veritas/flexsnap-datamover

   Note:

   Tag all the required images.

4. Use the following command to push all the tagged images:

   docker push container_registry_name/target_image_name:tag

   For example, docker push cpautomation.azurecr.io/veritas/flexsnap-deploy:10.3.0.0.1041

5. Edit the operator/kustomization.yaml file to reflect the new tag for flexsnap-operator pod.

   Update the newTag field under the cloudpointoperator.

6. Use the following command to apply the operator related change:

   kubectl apply -k operator -n <namespace>

7. Validate if the operator is updated or no:

   • Use the following command to obtain the pod name of flexsnap-operator:

     kubectl get pods -n <netbackup-operator-system>

   • To validate if the operator is updated or not:

     • Run the following command to obtain the pod name of flexsnap-operator:

       kubectl get pods -n <netbackup-operator-system>

     • Run one of the following to validate if the operator is updated or not:

       Describe the pod and check the events: kubectl describe pod <flexnsap_operator_pod_name> -n <netbackup-operator-system>

       Or

       To view the updated tag in the description: kubectl describe pod <flexnsap_operator_pod_name> -n <netbackup-operator-system> | grep -Image

8. Edit the environment.yaml file to reflect the new tag:

   tag: <SnapshotManager_EEB_version>

9. Update the NetBackup Snapshot Manager with the new tag:

   kubectl apply -f environment.yaml -n <environment_namespace>

10. To validate the upgrade of NetBackup Snapshot Manager:

    • Use the following commands to check the CRO status:

      kubectl get cpservers -n <environment_namespace>

      kubectl describe cpservers <cpserver_cro_name> -n <environment_namespace>

      For example, kubectl describe cpservers cpserver-1-224245 -n nbux

    • Use the following command to view the logs for successful upgrade and the upgraded version:

      kubectl logs -f <flexnsap_operator_pod_name> -n <netbackup-operator-system>

Post installation upgrade procedure using HELM charts

1. Perform steps 1 to 4 of 'EEB installation' procedure above.
2. Use the following command to update the new tag in flexsnap-operator:

   kubectl edit deployment flexsnap-operator -n <operator_namespace>

3. Validate if the operator is updated or no:

   • Use the following command to obtain the pod name of flexsnap-operator:

     kubectl get pods -n <netbackup-operator-system>

   • To validate if the operator is updated or not:

     • Run the following command to obtain the pod name of flexsnap-operator:

       kubectl get pods -n <netbackup-operator-system>

     • Run one of the following to validate if the operator is updated or not:

       Describe the pod and check the events: kubectl describe pod <flexnsap_operator_pod_name> -n <netbackup-operator-system>

       Or

       To view the updated tag in the description: kubectl describe pod <flexnsap_operator_pod_name> -n <netbackup-operator-system> | grep -Image

4. Use the following command to edit the new tag in cpServer section of environment custom resource:

   • Obtain the environment custom resource name: kubectl get environment -n <environment_namespace>

   • Edit the tag: kubectl edit environment <environment_CRname> -n <environment_namespace>

5. To validate the upgrade of NetBackup Snapshot Manager:

   • Use the following commands to check the CRO status:

     kubectl get cpservers -n <environment_namespace>

     kubectl describe cpservers <cpserver_cro_name> -n <environment_namespace>

     For example, kubectl describe cpservers cpserver-1-224245 -n nbux

   • Use the following command to view the logs for successful upgrade and the upgraded version:

     kubectl logs -f <flexnsap_operator_pod_name> -n <netbackup-operator-system>