NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
- Introduction to NetBackup on AKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on AKS
- Recommendations of NetBackup deployment on AKS
- Limitations of NetBackup deployment on AKS
- About primary server CR and media server CR
- Monitoring the status of the CRs
- Updating the CRs
- Deleting the CRs
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the node pool for primary or media servers
- Upgrading NetBackup
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Troubleshooting
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Pod restart failure due to liveness probe time-out
- 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 inconsistency in file ownership
- 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
- Appendix A. CR template
Monitoring the status of the 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. | ||
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. | ||
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. | ||
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:
|