Troubleshooting NetBackup servers with short names
- If NetBackup Kubernetes operator is not able to resolve backup server or media server based on short names, perform the following steps:
While fetching certificates if you get a message, EXIT STATUS 8500: Connection with the web service was not established. Then confirm from the nbcert logs whether hostname resolution successful or not. If it has failed, then perform the following steps:
Update the Kubernetes operator
deployment.yamland add thehostAliasesin the deployment.In the following
hostAliasesexample,backupserver.sample.domain.com and mediaserver.sample.domain.com are the hostnames of NetBackup primary and media server.
IP: 10.20.12.13 and IP: 10.21.12.13 are the IP addresses of NetBackup primary and media server.
hostAliases: - hostnames: - backupserver.sample.domain.com ip: 10.20.12.13 - hostnames: - mediaserver.sample.domain.com ip: 10.21.12.13
Copy, paste the hostAliases example details in the text editor and add to the hostAliases in the deployment.
- If data mover is not able to resolve short names of backup server or media server. To resolve this issue, perform the following steps:
Update configmap with backup server name.
Add datamover.hostaliases field, map with IP addresses to the hostname.
In the following
configmap.yamlexample,backupserver.sample.domain.com and mediaserver.sample.domain.com are the hostnames of NetBackup primary and media server.
IP: 10.20.12.13 and IP: 10.21.12.13 are the IP addresses of NetBackup primary and media server.
apiVersion: v1 data: datamover.hostaliases: | 10.20.12.13=backupserver.sample.domain.com 10.21.12.13=mediaserver.sample.domain.com datamover.properties: | image=reg.domain.com/datamover/image:latest version: "1" kind: configmap metadata: name: backupserver.sample.domain.com namespace: kops-nsCopy the
configmap.yamlfile details.Open the text editor and past the yaml file details.
Then, save it with the yaml file extension to the home directory from where the Kubernetes clusters are accessible.
To create the
configmap.yamlfile, run the command kubectl create -f configmap.yaml.if you update the
configmap.yamlwhich is already created then run the command to update configmap. kubectl apply -f configmap.yaml