NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Section II. Deployment
- Section III. Monitoring and Management
- Monitoring NetBackup
- Monitoring Snapshot Manager
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for Primary and Media servers
- 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
- Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq
- Post Kubernetes cluster restart, issues observed in case of containerized Postgres deployment
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Upgrading MSDP Scaleout
From NetBackup version 10.4 onwards, upgrade MSDP Scaleout based on the following conditions of NetBackup environment operator:
If MSDP Scaleout is deployed and controlled by NetBackup environment operator, then refer to the procedure in the following section to upgrade MSDP Scaleout along with other NetBackup applications:
Or
If MSDP Scaleout is deployed without the NetBackup environment operator, then follow the procedure described in this section below.
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.
See Installing the docker images and binaries for MSDP Scaleout.
- 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>
- 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.
- 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>
- 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.
More Information
Upgrading Cloud Scale deployment for Postgres using Helm charts