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
- Cloud Scale Disaster Recovery
- 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
Monitoring Primary/Media server CRs
You can view the status and other details of the primary server and media server CRs using the following commands:
kubectl get <PrimaryServer/MediaServer> -n <namespace> or
kubectl describe <PrimaryServer/MediaServer> <CR name> -n <namespace>
Following table describes the primary server CR and media server CR status fields:
Table:
Section | Field / Value | Description |
|---|---|---|
Primary Server Details Only one hostname and IP address for the respective primary server. | Host Name | Name of the primary server that should be used to access the web UI. |
IP | IP address to access the primary server. | |
Version | This indicates that the NetBackup primary server version is installed. | |
Media Server Details Number of hostname and IP address is equal to the replica count mentioned CR spec. | Host Name | Name of the media server. |
IP | IP address to access the media server. | |
Version | This indicates that the NetBackup media server version is installed. | |
Attributes | Resource Name | Statefulset name of the respective server. |
Primary/Media server name | Name of the primary server or media server deployed. | |
Config checker status | Indicates the status of the config checker as passed, failed, or skipped. For more information on the Config-Checker, See How does the Config-Checker utility work. | |
SHA Fingerprint | Represents the SHA key fingerprint of the NetBackup primary server. Note: SHAFingerprint represents the SHA256 CA certificate fingerprint of the primary server. | |
ElasticityAttributes | Describes the attributes associated with the media server autoscaler. For more information on the elasticity attributes, See Elastic media server. | |
Error Details | Code | A code assigned to an error encountered during the CR deployment or during the config-check operation. For more information on the error, refer to the NetBackup Status Code Reference Guide. |
Message | Message that describes the respective error code. | |
State | Success /Paused /Failed /Running | Current state of the custom resource, from one of the following:
|
Events | INIT/FAILOVER/UPGRADE | The events like INIT, FAILOVER and UPGRADE are logged in here. The details of these events can also be added. |
Services |
| This field indicates the status of the pods, their running state, image tag used and name of the service. |