NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Preparing the environment for NetBackup installation on Kubernetes cluster
- Recommendations of NetBackup deployment on Kubernetes cluster
- Limitations of NetBackup deployment on Kubernetes cluster
- Primary and media server CR
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the cloud node for primary or media servers
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying MSDP Scaleout
- Prerequisites for AKS
- Prerequisites for EKS
- Installing the docker images and binaries
- Initializing the MSDP operator
- Configuring MSDP Scaleout
- Using MSDP Scaleout as a single storage pool in NetBackup
- Configuring the MSDP cloud in MSDP Scaleout
- Using S3 service in MSDP Scaleout for AKS
- Enabling MSDP S3 service after MSDP Scaleout is deployed for AKS
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Socket connection failure
- Resolving an invalid license key issue
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Resolving the certificate error issue in NetBackup operator pod logs
- Pod restart failure due to liveness probe time-out
- NetBackup messaging queue broker take more time to start
- Host mapping conflict in NetBackup
- Issue with capacity licensing reporting which takes longer time
- Local connection is getting treated as insecure connection
- Primary pod is in pending state for a long duration
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Elastic media server related issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Restoring a catalog
You can restore a catalog.
To restore a catalog
- Copy DRPackages files (packages) located at
/mnt/nblogs/DRPackages/from the pod to the host machine from where Kubernetes Service cluster is accessed.Run the kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine> command.
- Preserve the data of
/mnt/nbdataand/mnt/nblogson host machine by creating tar and copying it using the kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data> command. - Change CR spec from paused: false to paused: true in primary, mediaServers, and msdpScaleouts sections in environment object using the following command:
kubectl edit <environment_CR_name> -n <namespace>
- Change replica count to 0 in primary server's statefulset using the kubectl edit statefulset <primary-server-statefulset-name> -n <namespace> command.
- Get names of PV attached to primary server PVC (catalog, log and data) using the kubectl get pvc -n <namespace> -o wide command.
- Delete primary server PVC (catalog, log and data) using the kubectl delete pvc <pvc-name> -n <namespace> command.
- Delete the PV linked to primary server PVC using the kubectl delete pv <pv-name> command.
- (EKS-specific) Navigate to mounted EFS directory and delete the content from primary_catalog folder by running the rm -rf /efs/* command.
- Change CR spec paused: true to paused: false in primary server section in and reapply yaml with the kubectl apply -f environment.yaml -n <namespace> command.
- After the primary server pod is in ready state, change CR spec from paused: false to paused: true in primary server section in environment object using the following command:
kubectl edit <environment_CR_name> -n <namespace> command.
- Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.
Increase the debug logs level on primary server.
Create a directory
DRPackagesat persisted location usingmkdir /mnt/nblogs/DRPackages.Change ownership of the
DRPackagesfolder to service user using the chown nbsvcusr:nbsvcusr /mnt/nblogs/DRPackages command.
- Copy earlier copied DR files to primary pod at
/mnt/nblogs/DRPackagesusing the kubectl cp <Path_of_DRPackages_on_host_machine> <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages command. - Execute the following steps in the primary server pod.
Change ownership of files in
/mnt/nblogs/DRPackagesusing the chown nbsvcusr:nbsvcusr <file-name> command.Deactivate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health deactivate command.
Stop the NetBackup services using
/usr/openv/netbackup/bin/bp.kill_all.Execute the nbhostidentity -import -infile /mnt/nblogs/DRPackages/<filename>.drpkg command.
Restart all the NetBackup services using
/usr/openv/netbackup/bin/bp.start_all.
- Verify security settings are back.
- Add respective media server entry in host properties using NetBackup Administration Console.
Navigate to NetBackup Management > Host properties > Master Server > Add Additional server and add media server.
- Restart the NetBackup services in primary server pod and external media server.
Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the same using the /usr/openv/netbackup/bin/bp.start_all command.
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command on the external media server.
- Configure a storage unit on external media server that is used during catalog backup.
- Perform catalog recovery from NetBackup Administration Console.
For more information, refer to the NetBackup Troubleshooting Guide.
- Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.
Stop the NetBackup services using the /usr/openv/netbackup/bin/bp.kill_all command.
Start NetBackup services using the /usr/openv/netbackup/bin/bp.start_all command.
Activate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health activate command.
- Change CR spec from paused: true to paused: false in primary, mediaServers, and msdpScaleouts sections in environment object using the following command:
kubectl edit <environment_CR_name> -n <namespace>
- To configure NetBackup IT Analytics refer to the following topic.
See Configuring NetBackup IT Analytics for NetBackup deployment.