Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
Last Published:
2022-06-27
Product(s):
NetBackup (10.0.0.1)
- 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
View the list of operator resources
To view all the operator resources, execute the following command on Kubernetes cluster:
$ kubectl get all -n netbackup-operator-system
The output should be something like this:
NAME READY STATUS RESTARTS AGE
pod/msdp-operator-controller-manager-65d8fd7c4d-whqpm 2/2 Running 0 3h6m
pod/netbackup-operator-controller-manager-55d6bf59c8-vltmp 2/2 Running 0 93m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/msdp-operator- ClusterIP 10.96.144.99 <none> 8443/TCP 3h6m
controller-manager-
metrics-service
service/msdp-operator- ClusterIP 10.96.74.75 <none> 443/TCP 3h6m
webhook-service
service/netbackup- ClusterIP 10.96.104.94 <none> 8443/TCP 93m
operator-controller
-manager-metrics-service
service/netbackup- ClusterIP 10.96.210.26 <none> 443/TCP 93m
operator-webhook-service
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/msdp- 1/1 1 1 3h6m
operator-controller-manager
deployment.apps/netbackup 1/1 1 1 93m
-operator-controller-manager
NAME DESIRED CURRENT READY AGE
replicaset.apps/msdp- 1 1 1 3h6m
operator-controller-
manager-65d8fd7c4d
replicaset.apps/netbackup- 1 1 1 93m
operator-controller-manager-
55d6bf59c8 Verify that both pods display Running in the Status column and both deployments display 2/2 in the Ready column.