Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Unable to run host properties on NB 7.1.0.4 hosts even though backups complete successfully

Created: 07 May 2012 • Updated: 13 May 2012 | 19 comments
Tina_K's picture
This issue has been solved. See solution.

Has anyone come across the same problem as stated above.

Steps undertaken to resolve:

1. I have applied a new eval key which is current on the master and media servers

Master (Solaris) and Media (Win).

Hosts are all upto date with 7.1.0.4 client.

2. Have even tried re-installing the client on one of the hosts.

Although I believe this is coincidental, the master server was moved to a production environment.

What I don't understand is that backups are completing successfully, and yet when I try to run a host properties it fails with a (25) Socket Error.

 

Comments 19 CommentsJump to latest comment

muhanad.daher's picture

Do you have a firewall?

check the netbackup ports 13724, 14780, 1556, must be open

Regards,

Muhanad Daher

Senior Data Center Engineer

SOLUTION
Tina_K's picture

Hi Muhanad,

Thank you for your prompt reply, I'd appreciate any assistance you can provide.

The ports are open.

Cheers,

Tina

muhanad.daher's picture

hi tina,

try this steps:

1- create a bpcd log file in cany of clients that you have status 25 (/usr/openv/netbackup/logs)

2- bpclntcmd –pn

3- bpclntcmd –hn <master server>

4- bpclntcmd –ip <IP_masterserver>

5- bpclntcmd -self

6- bptestbpcd.exe -verbose -M client_name.

 

print all out put, but for step 6 please go logs/bpcd/****.log; and print the out put

Regards,

Muhanad Daher

Senior Data Center Engineer

Tina_K's picture

I'll run the steps first thing tomorrow morning and confirm output.

Thanks again.

Tina_K's picture

Hi Muhanad,

Where should the above steps be run from? Media Server or Client?

muhanad.daher's picture

don't forget to restart the netbackup services on client

Regards,

Muhanad Daher

Senior Data Center Engineer

revaroo's picture

Are the backups of these clients being done by the Master server or by a media server?

Maybe the media servers can access the clients, but the Master cannot.

Answering this will help narrow the issue down.

Marianne's picture

I vote for revaroo's reply.

If you look at backup process flow diagram in Appendix A of Troubleshooting Guide, you will see that backups can be done with only media <-> client comms.
As long as you are not doing 'ALL_LOCAL_DRIVES or database agent backup, master and client never need to communicate.

To connect to client from master, ensure vnetd (13724) and PBX (1556) ports are open in both directions.
Ensure client can resolve master's IP address to hostname that appears in Client's SERVER list.

Unix servers are not always on DNS. Easiest is to add master to client's hosts file.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Tina_K's picture

Hi Marianne,

 

We are backing up "ALL_LOCAL_DRIVES".

I can run nslookup from the client for both the master and media servers successfully

both ports above are open on the Master and media servers

Marianne's picture

Create bpcd log on client. Try to connect again from Host Properties. Check bpcd log on client.

You can also post log as attachment - we will assist.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Tina_K's picture

Hi All,

I have attached the sanitized bpcd log for your analysis.

Thanks again for your assistance.

AttachmentSize
BPCD_LOG.txt 24.31 KB
Marianne's picture

At what time did you try to connect to Host Properties from the master?

There is no record of any connection attempt from the master, just media server:

14:54:15.731 [18240.20580] <2> logconnections: BPCD ACCEPT FROM (IP_MEDA_SERVER.169).58522 TO (IP_MEDA_SERVER.175).1556 fd = 528

 

Please try the following from master using cmd:

bptestbpcd -client <client-name> -verbose -debug

Please post output of command.

Also check if connection attempt can be seen in client's bpcd log.

 

**** EDIT ****

Please double-check 'sanitized' version of bpcd log. There is no reason for client to log connection from MEDIA to MEDIA. Connection should be from MEDIA to CLIENT:

BPCD ACCEPT FROM (IP_MEDA_SERVER.169).58522 TO (IP_MEDA_SERVER.175).1556

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Tina_K's picture

Hi Marianne,

Here's the output from the avbove command and the bpcd file was not updated

root@MASTER_SERVER# ./bptestbpcd -client CLIENT_SERVER -verbose -debug
16:40:10.313 [28757] <2> bptestbpcd: VERBOSE = 0
16:43:55.077 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
16:44:07.106 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
16:44:19.137 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
16:45:11.568 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
16:45:11.568 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
16:45:11.568 [28757] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
16:45:11.568 [28757] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
16:45:11.568 [28757] <2> vnet_connect_to_bpcd: ../../libvlibs/vnet_connect.c.237: 0: connect_to_service() failed: 18 0x00000012
16:45:11.568 [28757] <2> local_bpcr_connect: Can't connect to client CLIENT_SERVER
16:45:11.569 [28757] <2> ConnectToBPCD: bpcd_connect_and_verify(CLIENT_SERVER, CLIENT_SERVER ) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(CLIENT_SERVER ) failed: 25
16:45:11.569 [28757] <16> bptestbpcd main: Function ConnectToBPCD(CLIENT_SERVER ) failed: 25
<2>bptestbpcd: cannot connect on socket
16:45:11.569 [28757] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
16:45:11.569 [28757] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
root@MASTER_SERVER#

 

muhanad.daher's picture

you are right Marianne, i think he use media server agent and run from itself, there is no any connection between media to master.

Run the cmd from the master.

Regards,

Muhanad Daher

Senior Data Center Engineer

muhanad.daher's picture

Are there more than an IP address on the client?

in case yes, try this; in bp.conf insert REQUIRED_INTERFACE = IP_ADDR

 

 Are Firewall port is open?

in case No, try to open both directions - pbx (1556) and vnetd (13724), also stop Windows Firewall if available.

Regards,

Muhanad Daher

Senior Data Center Engineer

Tina_K's picture

Hi Muhanad and Marianne,

 

You both rock, with the clients being on separate vlans we didn't have firewall rules opened/configured on all of them.

Once, we had them opened we were able to run host properties.

Thank you both for your assistance with the resolution of this problem.

Cheers,

Tina

Mark_Solutions's picture

I know you have edited the logs - but did the CLIENT and SERVER display as short netbios or FQDN names? This can make a difference and you may need to use hosts files (Master, Media and  Clients) or add additional server names to your clients server lists

 

Hope this helps

 

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

Let us give credit where it's due - I have moved the solution to Muhanad's post since he suggested firewall ports right from the start.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links