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.
(AKS-specific): $ bash nbbuilder.sh -registry_name testregistry.azurecr.io -list_installed_eebs -nb_src_tag=10.3 -msdp_src_tag=18.0
(EKS-specific): $ bash nbbuilder.sh -registry_name <account id>.dkr.ecr.<region>.amazonaws.com -list_installed_eebs -nb_src_tag=10.3 -msdp_src_tag=18.0
Sample output:
Wed Feb 2 20:48:13 UTC 2022: Listing strings for EEBs installed in <account id>.dkr.ecr.<region>.amazonaws.com/netbackup/main:10.3. EEB_NetBackup_10.3Beta6_PET3980928_SET3992004_EEB1 EEB_NetBackup_10.3Beta6_PET3980928_SET3992021_EEB1 EEB_NetBackup_10.3Beta6_PET3980928_SET3992022_EEB1 EEB_NetBackup_10.3Beta6_PET3980928_SET3992023_EEB1 EEB_NetBackup_10.3Beta6_PET3992020_SET3992019_EEB2 EEB_NetBackup_10.3Beta6_PET3980928_SET3992009_EEB2 EEB_NetBackup_10.3Beta6_PET3980928_SET3992016_EEB1 EEB_NetBackup_10.3Beta6_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 <account id>.dkr.ecr.<region>.amazonaws.com/uss-controller:18.0. EEB_MSDP_18.0_PET3980928_SET3992007_EEB1 EEB_MSDP_18.0_PET3992020_SET3992019_EEB2 EEB_MSDP_18.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 <account id>.dkr.ecr.<region>.amazonaws.com/uss-engine:18.0. EEB_MSDP_18.0_PET3980928_SET3992006_EEB1 EEB_MSDP_18.0_PET3980928_SET3992023_EEB1 EEB_MSDP_18.0_PET3992020_SET3992019_EEB2 EEB_MSDP_18.0_PET3980928_SET3992009_EEB2 EEB_MSDP_18.0_PET3980928_SET3992010_EEB2 EEB_MSDP_18.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 <account id>.dkr.ecr.<region>.amazonaws.com/uss-mds:18.0. EEB_MSDP_18.0_PET3980928_SET3992008_EEB1 EEB_MSDP_18.0_PET3992020_SET3992019_EEB2 EEB_MSDP_18.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.3Beta6_PET3980928_SET3992021_EEB1 EEB_NetBackup_10.3Beta6_PET3980928_SET3992022_EEB1 EEB_NetBackup_10.3Beta6_PET3980928_SET3992023_EEB1 EEB_NetBackup_10.3Beta6_PET3992020_SET3992019_EEB2 EEB_NetBackup_10.3Beta6_PET3980928_SET3992009_EEB2 EEB_NetBackup_10.3Beta6_PET3980928_SET3992016_EEB1 EEB_NetBackup_10.3Beta6_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