Label a valid storage class for NetBackup usage, Add below label/labels based on VolumeModes ( Block/Filesystem) supported by storage class.

If NetBackup labeled storage class is not found then Backup from snapshot and Restore from backup copy fails with an error message No eligible storage classes found.

To label the storage classes, run the following commands given in the examples:

Example 1. Run the command:# kubectl get sc

Example 2. Run the command:# kubectl get sc ocs-storagecluster-ceph-rbd --show-labels

Example 3. Run the command: oc label storageclass ocs-storagecluster-cephfs netbackup.veritas.com/default-csi-storage-class=true

storageclass.storage.k8s.io/ocs-storagecluster-cephfs labeled

Example 4. Run the command:kubectl get sc ocs-storagecluster-cephfs --show-labels

Label a valid volume snapshot class for NetBackup usage, add the following label: netbackup.veritas.com/default-csi-volume-snapshot-class=true. If the NetBackup labeled VolumeSnapshotClass class is not found, then backup from snapshot job for metadata image and restore jobs fails with an error message: Failed to create snapshot of the Kubernetes namespace.

To label the volume snapshot classes, run the following commands given the examples:

Example 1. Run the command:# kubectl get volumesnapshotclass

Example 2. Run the command:# kubectl get volumesnapshotclass ocs-storagecluster-cephfsplugin-snapclass --show-labels

Example 3. Run the command:# kubectl label volumesnapshotclass ocs-storagecluster-cephfsplugin-snapclass netbackup.veritas.com/default-csi-volume-snapshot-class=true

volumesnapshotclass.snapshot.storage.k8s.io/ocs-storagecluster-cephfsplugin-snapclass labeled

Example 4. Run the command:# kubectl get volumesnapshotclass ocs-storagecluster-cephfsplugin-snapclass --show-labels

Each primary server which runs the backup from snapshot and restore from backup copy operations, needs to create a separate ConfigMap with the primary server's name.

In the following configmap.yaml example,

apiVersion: v1
data:
  datamover.hostaliases: |
        10.20.12.13=backupserver.sample.domain.com
        10.21.12.13=mediaserver.sample.domain.com
  datamover.properties: |
        image=reg.domain.com/datamover/image:latest
  version: "1"
kind: ConfigMap
metadata:
  name: backupserver.sample.domain.com
  namespace: kops-ns

Specify datamover.properties: image=reg.domain.com/datamover/image:latest with correct datamover image.

Specify datamover.hostaliases, if the primary server and the media servers connected to the primary server have short names and host resolution failing from datamover. Provide a mapping of all hostnames to IPs for primary and media servers.

Create a secret as described in detail in the Point 6 in the Deploy service package on NetBackup Kubernetes operator section to use a private docker registry.

Once the secret is created, add the following attributes while creating a configmap.yaml file.

datamover.properties: | image=repo.azurecr.io/netbackup/datamover:10.0.0049 imagePullSecret=secret_name

Create the configmap.yaml file, run the command: kubectl create -f configmap.yaml.

If Kubernetes operator is not able to resolve the primary server based on short names

Create a secret with fingerprint and authorization token.

For more information about creating the secret and backupservercert, refer to the section Deploying certificates on NetBackup Kubernetes operator in the NetBackup™ Web UI Kubernetes Administrator's Guide

Create a backupservercert request to fetch certificates.

For more information, refer to Deploying certificates on NetBackup Kubernetes operatorin the NetBackup™ Web UI Kubernetes Administrator's Guide

For more information, refer to the NetBackup™ Security and Encryption Guide.