Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
Last Published:
2022-09-08
Product(s):
NetBackup (10.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 Snapshot Manager
- Migration and upgrade of Snapshot Manager
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager deployment
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Uninstalling Snapshot Manager
- 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 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
- Data migration unsuccessful even after changing the storage class through the storage yaml file
- Host validation failed on the target host
- Primary pod is in pending state for a long duration
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Host mapping conflict in NetBackup
- NetBackup messaging queue broker take more time to start
- Local connection is getting treated as insecure connection
- Issue with capacity licensing reporting which takes longer time
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Primary pod goes in non-ready state
- Appendix A. CR template
Getting EEB information from an image, a running container, or persistent data
To view the list of installed EEBs, run the nbbuilder script provided in the EEB file archive.
$ bash nbbuilder.sh -registry_name testregistry.azurecr.io -list_installed_eebs -nb_src_tag=10.1-2 -msdp_src_tag=17.0-2
Sample output:
Wed Feb 2 20:48:13 UTC 2022: Listing strings for EEBs installed in testregistry.azurecr.io/netbackup/main:10.1-2. EEB_NetBackup_10.1Beta6_PET3980928_SET3992004_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992021_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992022_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992023_EEB1 EEB_NetBackup_10.1Beta6_PET3992020_SET3992019_EEB2 EEB_NetBackup_10.1Beta6_PET3980928_SET3992009_EEB2 EEB_NetBackup_10.1Beta6_PET3980928_SET3992016_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992017_EEB1 Wed Feb 2 20:48:13 UTC 2022: End Wed Feb 2 20:48:13 UTC 2022: Listing strings for EEBs installed in testregistry.azurecr.io/uss-controller:17.0-2. EEB_MSDP_17.0_PET3980928_SET3992007_EEB1 EEB_MSDP_17.0_PET3992020_SET3992019_EEB2 EEB_MSDP_17.0_PET3980928_SET3992010_EEB2 Wed Feb 2 20:48:14 UTC 2022: End Wed Feb 2 20:48:14 UTC 2022: Listing strings for EEBs installed in testregistry.azurecr.io/uss-engine:17.0-2. EEB_MSDP_17.0_PET3980928_SET3992006_EEB1 EEB_MSDP_17.0_PET3980928_SET3992023_EEB1 EEB_MSDP_17.0_PET3992020_SET3992019_EEB2 EEB_MSDP_17.0_PET3980928_SET3992009_EEB2 EEB_MSDP_17.0_PET3980928_SET3992010_EEB2 EEB_MSDP_17.0_PET3980928_SET3992018_EEB1 Wed Feb 2 20:48:14 UTC 2022: End Wed Feb 2 20:48:14 UTC 2022: Listing strings for EEBs installed in testregistry.azurecr.io/uss-mds:17.0-2. EEB_MSDP_17.0_PET3980928_SET3992008_EEB1 EEB_MSDP_17.0_PET3992020_SET3992019_EEB2 EEB_MSDP_17.0_PET3980928_SET3992010_EEB2 Wed Feb 2 20:48:15 UTC 2022: End
Alternatively, if the nbbuilder script is not available, you can view the installed EEBs by executing the following command:
$ docker run --rm <image_name>:<image_tag> cat /usr/openv/pack/pack.summary
Sample output:
EEB_NetBackup_10.1Beta6_PET3980928_SET3992004_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992021_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992022_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992023_EEB1 EEB_NetBackup_10.1Beta6_PET3992020_SET3992019_EEB2 EEB_NetBackup_10.1Beta6_PET3980928_SET3992009_EEB2 EEB_NetBackup_10.1Beta6_PET3980928_SET3992016_EEB1 EEB_NetBackup_10.1Beta6_PET3980928_SET3992017_EEB1
To view all EEBs installed in a running container, run:
$ kubectl exec --stdin --tty <primary-pod-name> -n <namespace> -- cat /usr/openv/pack/pack.summary
Note:
The pack directory may be located in different locations in the uss-* containers. For example: /uss-controller/pack , /uss-mds/pack, /uss-proxy/pack.
To view a list of installed data EEBs from a running container, run:
$ kubectl exec --stdin --tty <primary-pod-name> -n <namespace> -- cat /mnt/nbdata/usr/openv/pack/pack.summary