Please enter search query.
Search <book_title>...
NetBackup™ Web UI Kubernetes Administrator's Guide
Last Published:
2022-10-28
Product(s):
NetBackup (10.1)
- Overview of NetBackup for Kubernetes
- Deploying and configuring the NetBackup Kubernetes operator
- 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 datamover
- Configure settings for NetBackup snapshot operation
- Troubleshooting NetBackup servers with short names
- Managing image groups
- Deploying certificates on NetBackup Kubernetes operator
- Managing Kubernetes assets
- Managing Kubernetes intelligent groups
- Protecting Kubernetes assets
- Recovering Kubernetes assets
- 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
Configure NetBackup Kubernetes datamover
You need to configure datamover for the NetBackup Kubernetes workload. Download the correct version of the datamover image: veritasnetbackup-datamover-10.0-0070.tar for your release version, from the download center. See https://www.veritas.com/content/support
To configure datamover
- To push the datamover image to docker 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>
- Ensure that the configmap with primary server name, have image value set to <repo-name/image-name:tag-name> pushed in step no 4.
For more details on configmap, See Prerequisites for backup from snapshot and restore from backup operations.