NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

PVC

CatlogPVC.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: catalog
  namespace: ns-155
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: ""
  resources:
    requests:
      storage: 100Gi
  volumeName: environment-pv-primary -catalog

PV

catalogPV

apiVersion: v1
kind: PersistentVolume
metadata:
  name: environment-pv-primary-catalog
  labels:
    topology.kubernetes.io/region: us-east-2 # Give the region as your configuration in your cluster
    topology.kubernetes.io/zone: us-east-2c # Give the zone of your node instance, 

can also check with subnet zone in which your node instance is there.
spec:
  capacity:
    storage: 100Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  storageClassName: ""
  persistentVolumeReclaimPolicy: Retain
  mountOptions:
    - iam
  csi:
    driver: efs.csi.aws.com
    volumeHandle: fs-07a82a46b4a7d87f8:/nbdata  #EFS id need to be changed as per your created EFS id
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: catalog  # catalog pvc name to which data to be copied namespace: ns-155

To get statefulset name: kubectl get sts -n < namespace in environment cr (ns-155)>

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

Follow the naming conventions of static PV and PVC to consume for Primary Server Deployment.

catalog-<Name_of_primary>-primary-0
data-<Name_of_primary>-primary-0
Example:
catalog-test-env-primary-0
data-test-env-primary-0
environment.yaml
apiVersion: netbackup.veritas.com/v2
kind: Environment
metadata:
name: test-env
namespace: ns-155
spec:
...
   primary:
     # Set name to control the name of the primary server.
The default value is the same as the Environment's metadata.name.
     name: test-env

Yaml to create new catalog PVC:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: catalog-test-env-primary-0
  namespace: ns-155
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: ""
  resources:
    requests:
      storage: 100Gi
  volumeName: environment-pv-primary-catalog

To get PVC details: kubectl get pvc -n < Namespace>

Use edit command to get PVC details: kubectl edit pvc < New PVC(old name) name > -n < Namespace >

To get PV details: kubectl edit pv < PV name (in which data is copied) >

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

Change the storage class for catalog under primary section to catalog and log PV name respectively Set the paused=false under primary section.

Change the strorageClass for data and logs as with storageClassName and 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