Search <book_title>...

NetBackup™ Web UI Kubernetes Administrator's Guide

Last Published: 2022-12-19

Product(s): NetBackup (10.1.1)

Configure settings for NetBackup snapshot operation

You need to configure snapshot operation on the Kubernetes operator deployment before you perform the actual backup from snapshot operations.

Define a storage class pointing to the CSI plugin.
Define a VolumeSnapshotClass class consisting of CSI driver details.
Label the volume snapshot class for NetBackup usage.
Add the following label netbackup.veritas.com/default-csi-volume-snapshot-class=true.
- The volume snapshot class label netbackup.veritas.com/default-csi-volume-snapshot-class=true is used to label all the CSI volume snapshot class which user wants to use for snapshot operation.
Note:
Snapshot of a namespace consisting of persistent volume fails with an error message: Failed to create snapshot of the Kubernetes namespace.
The snapshot operation may fail due to multiple reasons, for example, a valid volume snapshot class for the driver with label volumesnapshotclass is not found.
Label the CSI Storage classes on the kubernetes cluster.
Add the following label netbackup.veritas.com/default-csi-filesystem-storage-class=true.
- The storage class labels netbackup.veritas.com/default-csi-storage-class: "true" is used to label where storage class provisions volumes based on raw block.
- The new storage class label netbackup.veritas.com/default-csi-filesystem-storage-class=true is used to label where storage class provisions volumes based on file system.
Note:
You can add both labels on a single storage class. If the storage class supports Block volume backed by raw block and the Filesystem volume.
Sizing for metadata persistent volume is required. The default persistent volume size for Kubernetes operator is 10Gi. The persistent volume size is configurable.
You can change the value for storage from 10Gi to a higher value before deploying the plugin. This leads to the nbukops pod have the size of the PVC mounted in the pod.
Persistent Volume Claim looks like this:
```
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  labels:
    component: netbackup
  name: {{ .Release.Namespace }}-netbackupkops
  namespace: {{ .Release.Namespace }}
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
```
- During fresh installation while configuring the Helm Chart. You can modify the size of PVC storage in the deployment.yaml of the netbackupkops-helm-chart which leads to creation of the initial PVC size.
- Post installation, updating the PVC size (dynamic volume expansion) is supported by few storage vendors. For more information, refer to https://kubernetes.io/docs/concepts/storage/persistent-volumes

Note:

The default size of persistent volume can be resized to larger value without losing the data. You are recommended to add the storage provider that supports volume expansion.

Note:

To get the configuration value, you can run the command: kubectl get configmaps <namespace>-backup-operator-configuration -n <namespace> -o yaml > {local.file}