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
- Customize Kubernetes workload
- 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 NetBackup Kubernetes data mover
You need to configure data mover for the NetBackup Kubernetes workload. Download the correct version of the data mover image:
You need to configure Netbackup Kubernetes Operator namespace to support Backup from Snapshot and Restore from Backup. (Backup copy). Download the correct version of the data mover image:veritasnetbackup-datamover-11.0.tarfor your release version, from the download center. See https://www.veritas.com/content/support
To configure data mover
- To push the data mover image to image registry, run the command:
docker login -u <user name> <repo-name>
- Enter the password upon prompt. Skip this step if you are already logged in
- Run docker load -i <name of the datamover image file>
- Run docker tag <datamover image name:tag of the loaded datamover image> <repo-name/image-name:tag-name>
- docker push <repo-name/image-name:tag-name>
Note:
In the example, docker is used for reference. You can use any CLI tool which has equivalent capabilities.
- Ensure that the configmap with primary server name, have image value set to <repo-name/image-name:tag-name> pushed in step no 4.
Example,
apiVersion: v1 data: datamover.properties: image=<image-repo>/datamover:<datamover tag> version: "1" kind: ConfigMap metadata: name: <Primary Server Name> namespace: <Netbackup Kubernetes Operator Namespace Name>
For more details on Configmap, refer to the Kubernetes operators supported configuration parameters section in the NetBackup for Kubernetes Administrator's Guide..