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
Upgrade the NetBackup Kubernetes operator
You can upgrade the NetBackup Kubernetes operator deployment using Helm commands.
Example:
helm upgrade veritas-netbackupkops ./netbackupkops-helm-chart -n netbackup
Add note to backup configmap values if they are changed. Upgrade resets the helm values to default. Old configmap must be patched again after upgrade.
All components (NBU Primary, Media, Kubernetes operators, and Data mover) must be same version.
Existing policies continue to take backups but must be restored manually until the Kubernetes operator is updated.
Note:
This is applicable to the NetBackup version 9.1 to 10.x upgrade
To upgrade the NetBackup Kubernetes operator
- Download the tar package from Veritas Support website: https://www.veritas.com/support
- Extract the package to the home directory. The
netbackupkops-helm-chartfolder must be in the home directory. - To list all cluster contexts, run the command: kubectl config get-contexts
- To switch to the cluster where you want to deploy the operator service, run the command:kubectl config use-context <cluster-context-name>
- To change the current directory to your home directory, run the command: cd ~
- NetBackup supports any Container Image Repositories complied to OCI standards. you can use any tools to push the operators and data mover images. If you use a private docker registry, follow the instructions in this step to create a secret
nb-docker-credin NetBackup namespace. Otherwise, skip to the next step.To load the image to the docker cache and push the image to the docker image repository, run the commands:
Load the tar file for Netbackup Kubernetes operator.
<docker load -i <nameof the tar file> ./>Tag the loaded docker image as per requirement.
docker tag <imagename:tagof the loadedimage> <repo-name/image-name:tag-name>Push the image to a repository from where Kubernetes can fetch the image at the time of NetBackup Kubernetes operator deployment.
docker push <repo-name/image-name:tag-name>
Note:
In the example, a docker is used for reference. You can use any other CLI tool that provides equivalent functionality.
- Edit the
netbackupkops-helm-chart/values.yamlin a text editor:Replace the image value in the manager section with your image name and tag in the format
reponame/image-name:tag-name.Replace the datamover image in the
netbackup_config_podsection with datamover image name and tag.
- To upgrade the NetBackup Kubernetes operator, run the command:
helm upgrade <plugin-name> <chart-path> -n <namespace>
Example:
helm upgrade veritas-netbackupkops ./netbackupkops-helm-chart -n netbackup
Note:
Upgrading the NetBackup Kubernetes operator will reset the Helm values to their defaults. Ensure that you back up the old configmap and reapply any patches if the values change after the upgrade.