NetBackup status code: 21

[Ialahmad]

Hi All
I have Netbackup 6.5.4 system there is a problem appear on backup on windows server  2003 SP2 ,which is "Socket open failed"
client server in dmz network but there suceessfully backup done on same server in dmz.
please I need your advise.
kind regards.

[lu]

what's the output of 'bpgetconfig -g myclient' on the master ?

[Ialahmad]

HI lu
the output as shown below

C:\Documents and Settings\Administrator>bpgetconfig -g bareed01
socket open failed

C:\Documents and Settings\Administrator>

[Will_Restore]

make sure vnetd (13724) & pbx (1556) ports are open bidirectional


Port Usage Guide for Windows and UNIX Platforms
http://seer.entsupport.symantec.com/docs/281623.htm

[Jack_Sperow]

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create debug log directories for the processes that returned this status code. Then, retry the operation and check the resulting debug logs.

2. On Windows, verify that the recommended service packs are installed

[Ialahmad]

I tested vnetd (13724) & pbx (1556) ports and they  are opened in bidirectional way
by run commant
telnet client 13724

[Karthikeyan_Sun]

 Check your master server and client side hosts files, that should have proper entries with ip's.

Also make sure the ip resolving for host name ping is same as original...

[J_H_Is_gone]

1) verify that you have the client setup to use vnet.
master server properties
Client attributes
add server if not there
connection options
BPCD connection option = VNETD port

2) if not using hosts files ( a lot of people do not) verify that DNS has both a forward and reverse entry for the client - and that if you do a nslookup for the client by ip address you get back the same name  - meaning if you add the server as myserver.mynetwork.com and you do the nslookup by ip - if you get back myserver.dmznetwork.com - then it is not going to work - forward and reverse have to match.

[Marianne · Accepted solution]

Telnet only verifies connectivity in one direction (server -> client).
Use bptestbpcd to test 'connect back' as well.
Ensure bpcd log directory exists on client, then run 'bptestbpcd -client <client_name>'
Check bpcd log on client for errors.
For more info/options, see TN http://seer.entsupport.symantec.com/docs/277901.htm