Netbackup 7.1 cannot connect to client on a different windows domain
Helleu!
We have a Netbackup server running on a branch office site which facilitates the backup for 3 virtual servers...all working like a charm.
Now on the same site we''ve added 3 virtual servers for a joint-venture site...these servers are part of a different windows domain. Installation goes well (i can specify the user to install etc.), but once installed and i configure the client within the master server, it can''t connect to socket. I''ve made sure the clients are resolvable from the master server and the master server is resolvable on the clients. I suspect the cannot connect to socket error might be related to the difference in windows domain, but i don't know how to work around it. I can''t configure different authorisations for those clients on the master server, since it won''t let me bring up the properties without connecting to the client :-(
Anywaybody any ideas/willing to help?
Thank you in advance & kind regards,
Peter
Comments
Admin Console on master?
Are you working on the actual master server with the admin console? If not, then the workstation you run the admin console must be allowed on the client as well.
Windows firewall blocking VNETD, BPCD, PBX ports? You may have to add TCP port rules on the Windows firewall on the clients.
/A
Hi AAlmroth, I'm working on
Hi AAlmroth,
I'm working on the master server with the admin console...and all the windows firewall services have been disabled (on both the master server as well as the clients)... :-/
Kind regards,
Peter
NetBackup out of the box is
NetBackup out of the box is pure IP based - it doesnt care about Domains
As long as forward and reverse lookup works (host files are great for this) and you have at least 1556 open both ways between them then it should work
It is doesnt then check that there is no firewall between them (including that set on the ESX Server itself) and ensure that the NetBackup Client Service on the clients is running.
On the client set up a new directory at <installpath>\veritas\netbackup\logs\bpcd\ and then try connecting to it from the Master Server again and post the resulting log file created in that directory
Also on the client run <installpath>\veritas\netbackup\bin\bpclntcmd -sv and see if it gets a response
Let us know the results
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Hi Mark, Obviously i was
Hi Mark,
Obviously i was thinking it was windows domain related...that it's only IP related is new for me...learned something already, tnx!
As for the hosts file -> that's where i added the clients on the master server and the master server on the clients...and that seems to work fine.
Here's the output from your suggested stept regarding creating the log directory:
21:15:53.786 [2664.2440] <2> setup_debug_log: switched debug log file for bpcd
21:15:53.786 [2664.2440] <2> bpcd main: VERBOSE = 0
21:15:53.786 [2664.2440] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpcd.exe -standalone
21:15:53.786 [2664.2440] <2> process_requests: offset to GMT -28800
21:15:53.786 [2664.2440] <2> logconnections: BPCD ACCEPT FROM 192.168.10.10.4429 TO 192.168.10.24.1556 fd = 372
21:15:53.786 [2664.2440] <2> process_requests: setup_sockopts complete
21:15:53.786 [2664.2440] <2> bpcd peer_hostname: Connection from host sv1028.ballastham.com (192.168.10.10) port 4429
21:15:53.786 [2664.2440] <2> bpcd valid_server: comparing sv1028.ballastham.com and sv1028.ballastham.com
21:15:53.786 [2664.2440] <4> bpcd valid_server: hostname comparison succeeded
21:15:53.786 [2664.2440] <16> process_requests: read failed: The operation completed successfully.
And the <installpath>\veritas\netbackup\bin\bpclntcmd -sv command gives a "7.1" output....
It all looks so functional...yet...it's not :-(
Tnx in advance & kind regards,
Peter
It works!
Hi Mark,
Your added logging let me to this post: https://www-secure.symantec.com/connect/forums/nbu-701-status-25-socket-error-windows-clients-2008r2
Which describes hostname usage and them beeing unique to the interface - so i made extra hostnames for the 192.168.10.* links (this is the network dedicated for network traffic) on both the clients as well as the master.
I reinstalled all the client software based on these new hostnames and added the clients on the master server using the FQDN's. This however did not solve it..yet.... There was also a setting on the master server which SHOULD work, but didn't -> the 192.168.10.10 interface was set to be used in the master server properties...i had to remove that extry for it to work properly (which is quite strange, since the joint-venture servers can only reach the master server on that interface anyways.
Now it works, and i am a happy camper!
Thanks for both your (mark) help as well as all the others, appreciate it!
Kind regards,
Peter
The last line of the bpcd
The last line of the bpcd suggest that it accepts incoming messages but has an issue replying
Do you have what is needed open in both directions?
PBX - 1556, vnetd - 13724, bpcd - 13782 (though on 7.1 just 1556 should be OK)
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Peter, Is sv1028.ballastham.c
Peter,
Is sv1028.ballastham.com the name of a master server or media server? If not, try adding it that name to the server list on the client. Also, verify that the NBU ports are open in both directions on your network firewall.
I recently worked through a similar issue and this is how I resolved it.
1) is there a firewall
1) is there a firewall between domains? usually yes - you have to get the firewall to open those ports both ways between the other domain and your master/media servers
2) that pesky dns forward/reverse looking up. Make sure on the Client that you are using FQDN's for the master and media servers. And on the master in the policy use the FQDN for the clients.
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
test
test
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
Would you like to reply?
Login or Register to post your comment.