Hi guys,
I'm facing an issue with the backup selections for MS-Windows type policies that I want to create on NetBackup 7.6.1 and 8.1.
Getting message "Unable to connect to host".
I have tried many suggested solutions in the forum without success.
So I want to start a new discussion on my specific case.
Can I get any help?
Hello,
cause is usually on network level.
run bptestbpcd -host "host" from Master Server (and Media Server if applicable) to the client.
The same from client to Master (media).
Or simply telnet to port 1556, bidirectionally.
Run nslookups in both directions.
Add Backup selections manually (without browsing) and run backup. How does it end?
Well, finally, what does it mean - "NetBackup 7.6.1 and 8.1"? Dont you have higher version on the client than on the Master?
regards
Michal
Output of "run bptestbpcd -host "host" from Master Server (and Media Server if applicable) to the client."
C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -host client.name
<16>bptestbpcd main: Function ConnectToBPCD(client.name) failed
: 25
<16>bptestbpcd main: cannot connect on socket
cannot connect on socket
I took time to give output.
I did not find bptestbpcd on client side.
Telnet to port 1556 was ok, bidirectionally. Same for nslookup in both directions.
I did add manually backup selections and got error code 58 with backup jobs failing.
I'm currently facing the same issue on 2 different servers, one with version 7.6.1 and the other one with 8.1
Hello,
you can try adding the data of the client in the table host of the master and in the client the data of the master
You should also check that the firewall is disabled.
if this does not work you should check that the communication ports are open in the client
Greetings.
I did so.
Host tables, firewall and communication ports checked.
So you have some problem with communication to client:
C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -host client.name
<16>bptestbpcd main: Function ConnectToBPCD(client.name) failed
: 25
<16>bptestbpcd main: cannot connect on socket
cannot connect on socket
When telnet to client/1556 works, then there are 2 possible causes:
- NetBackup services on client are stopped (only pbx is running)
- reverse lookup of Master on the client is not configured
Michal
