Forum Discussion

mndbnbp's avatar
mndbnbp
Level 3
3 years ago

Unable to install Netbackup 9.1.0.1 client on Linux

Hello everyone.

I am Japanese.
I am using a translation web site to write this post.
So sorry if I am using wrong English.

I have now installed the Netbackup client on RHEL8.
I am getting an error that it cannot communicate with the master server.
The installation itself succeeds, but I cannot see the client when creating backup policies.

I have the security level set to "medium" on the Master Server, so I don't think I need a token.

The configuration is as follows

Master Server: Windows Server 2019 Standard
Client: RHEL 8
Netbackup(master server/client): 9.1.0.1
Installer: NetBackup_9.1.0.1_CLIENTS2.tar.gz


Error log during installation

Do you wish to continue? [y,n] (y)

The private_tmp value is /tmp/nbcheck_dir.1572

Checking for critical system conditions...

/tmp/NetBackup_9.1.0.1_CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat2.6.32/127.
WARNING: Unable to provide preinstall check results.

Do you want to install the NetBackup client software for this client?
This package will install Linux/RedHat2.6.32 client.
This package will install NetBackup client 9.1.0.1.
Enter the name of the NetBackup master server : server1

Would you like to use "client1" as the configured
Enter the name of the NetBackup master server : server1 Would you like to use "client1" as the configured name of the NetBackup client?

Successfully unpacked /tmp/NetBackup_9.1.0.1_CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/clienmdTool_for_UNIX.tar.gz.
NOTE: Depending on the network, this action may take a few minutes.
To continue without setting up secure communication, press Ctrl+C.
EXIT STATUS 103: error occurred during initialization, check configuration file

ERROR: Cannot set up secure communication.
The attempt to contact the master server failed.

Do you wish to proceed with installation even though NetBackup may not operate? [y,n]n


Please let me know how to resolve this issue.

Thanks.

 

  • hello

    Well this looks like name resolution related issue.

    Are you able to ping server1 from client1 and vice-versa? You need to sort out these name resolution - check with ping :)

    you can always map the IP and name in /etc/hosts file on linux or in c:\windows\system32\drivers\etc\hosts

    as a workaround....

     

  • Hi, 

    as mentionned by quebek  this looks like a name resolution / communication issue between the client and the master, often it is because of using shortnames instead of FQDN or vice versa..

    one more thing, make sure ports are opened biderectionnaly.

    you can process the install without certificate step, and once done, run nbcertcmd command to generate the certificate and by doing it, you may find the exact error/message.

     

    BR