NetBackup™ for Kubernetes Administrator's Guide
- Overview of NetBackup for Kubernetes
- Deploying and configuring the NetBackup Kubernetes operator
- Prerequisites for NetBackup Kubernetes Operator deployment
- Deploy service package on NetBackup Kubernetes operator
- Port requirements for Kubernetes operator deployment
- Upgrade the NetBackup Kubernetes operator
- Delete the NetBackup Kubernetes operator
- Configure NetBackup Kubernetes data mover
- Automated configuration of NetBackup protection for Kubernetes
- Configure settings for NetBackup snapshot operation
- Troubleshooting NetBackup servers with short names
- Data mover pod schedule mechanism support
- Validating accelerator storage class
- Deploying certificates on NetBackup Kubernetes operator
- Managing Kubernetes assets
- Managing Kubernetes intelligent groups
- Managing Kubernetes policies
- Protecting Kubernetes assets
- Managing image groups
- Protecting Rancher managed clusters in NetBackup
- Recovering Kubernetes assets
- About incremental backup and restore
- Enabling accelerator based backup
- Enabling FIPS mode in Kubernetes
- About Openshift Virtualization support
- Troubleshooting Kubernetes issues
- Error during the primary server upgrade: NBCheck fails
- Error during an old image restore: Operation fails
- Error during persistent volume recovery API
- Error during restore: Final job status shows partial failure
- Error during restore on the same namespace
- Datamover pods exceed the Kubernetes resource limit
- Error during restore: Job fails on the highly loaded cluster
- Custom Kubernetes role created for specific clusters cannot view the jobs
- Openshift creates blank non-selected PVCs while restoring applications installed from OperatorHub
- NetBackup Kubernetes operator become unresponsive if PID limit exceeds on the Kubernetes node
- Failure during edit cluster in NetBackup Kubernetes 10.1
- Backup or restore fails for large sized PVC
- Restore of namespace file mode PVCs to different file system partially fails
- Restore from backup copy fails with image inconsistency error
- Connectivity checks between NetBackup primary, media, and Kubernetes servers.
- Error during accelerator backup when there is no space available for track log
- Error during accelerator backup due to track log PVC creation failure
- Error during accelerator backup due to invalid accelerator storage class
- Error occurred during track log pod start
- Failed to setup the data mover instance for track log PVC operation
- Error to read track log storage class from configmap
Configure settings for NetBackup snapshot operation
You need to configure storage classes and volume snapshot class in order to protect the Persistent Volume Claims. After Netbackup Kubernetes Operator is installed, the following configuration needs to be done.
Identify the storage classes pointing to CSI plugin or if there is no storage class present then define a new storage class pointing to the CSI plugin.
Identify the Volume Snapshot Class pointing to CSI Plugin or If there is no volume snapshot class present then define a new volume snapshot class pointing to CSI plugin.
Define a VolumeSnapshotClass class consisting of CSI driver details.
Label the CSI Storage classes on the kubernetes cluster.
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 (volumeMode=Block).
The 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 (volumeMode=FileSystem).
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.
Label the CSI Volume Snapshot Class for Netbackup usage
The needsvolumesnapshotclasslabel netbackup.veritas.com/default-csi-storage-class=true is label that is required to add to all the CSI volumesnapshotclass 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 volumesnapshot class for the driver with valid label volumesnapshotclass is not found.