cancel
Showing results for 
Search instead for 
Did you mean: 

A socket could not be opened

Kevin_Gallagher
Level 3
I am using Netbackup Ver. 6.0 MP4.
I have a Master and Media server both on Windows and a client on SUSE 9.3.
The SUSE client was backing up successfully untill I migrated the VM that it runs under.
At that point the backups failed with a Status code 21 (A socket could not be opened.).
I can obtain the properties of the client but it takes some time. I timed the bpcltncmd -pn command on the client and the response was thus:
 
time ./bpclntcmd -pn
expecting response from server crl-nbmas-1
server1.napier.ac.uk server1 146.176.xxx.xxx 1820
real    0m30.880s
user    0m0.038s
sys     0m0.046s
 
I can nslookup/ping/traceroute the Master and Media servers successfully and quickly. I can also do bpclntcmd -hn and -ip quickly.
 
I am at a loss as to what is causing the problem. Can anyone suggest what I should look at. Do you think Netbackup needs to reregister the client and if so how do I achieve this?
1 REPLY 1

Anonymous
Not applicable

I wonder if you migrated the VM to a new ESX host and the firewall rules on this host are different to those on the previous.

esxcfg-firewall is the command to use to observe settings or use the vi client