Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-10-23
Product(s):
NetBackup (10.3.0.1, 10.3)
- 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
- Verifying Cloud Scale deployment
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Setting key parameters in Cloud Scale deployments
- Section III. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS 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 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
- Failed to register Snapshot Manager with NetBackup
- Pods unable to connect to flexsnap-rabbitmq post Kubernetes cluster restart
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Upgrading MSDP Scaleout
You can upgrade the MSDP Scaleout solution to the latest version in your AKS or EKS environment.
To upgrade MSDP Scaleout operator
- Install the new kubectl plug-in and push the new docker images to your container registry.
- Run the following command to upgrade the MSDP operator.
kubectl msdp init -i <new-operator-image> -s <storage-class-name> -l agentpool=<nodepool-name> -n <operator-namespace>
All the options except -i option must be same as earlier when the operator was deployed initially.
To upgrade MSDP Scaleout CR resources
- If you use the environment operator for the MSDP Scaleout deployment, run the following command to change the spec.msdpScaleouts[<index>].tag field in the existing CR resources:
kubectl edit environment <environmentCR_name> -n <cr-namespace>
- This step is applicable to AKS only.
If MSDP S3 service is enabled and you want to upgrade from NetBackup 10.2, you must provide the pre-allocated MSDP S3 FQDN and IP address in the spec.msdpScaleouts[<index>].s3Ip field.
See Enabling MSDP S3 service after MSDP Scaleout is deployed for AKS.
- If you use the MSDP operator for the MSDP Scaleout deployment, run the following command to change the spec.version in the existing CR resources.
kubectl edit msdpscaleout <cr-name> -n <cr-namespace>
- This step is applicable to AKS only.
If MSDP S3 service is enabled and you want to upgrade from NetBackup 10.2, you must provide the pre-allocated MSDP S3 FQDN and IP address in the spec.s3ServiceIPFQDN field.
Wait for a few minutes. MSDP operator upgrades all the pods and other MSDP Scaleout resources automatically.
- Upgrade process restarts the pods. The NetBackup jobs are interrupted during the process.