Netbackup error code 25

[kaka_wang]

platform :windows 2003

nbu version :6.5.5

one client cann't connect to master server about 1 month ago,error code is 25.

I tried to use bpclntcmd -pn on client , it could come back master server info ,but couldn't come back any client infomation.

and I tried to use bptestbpcd on master server ,also couldn't connect to client.

but I could telnet client port  13782 and 13724  from master server ,also from client to master.

ping also is OK.

open debug log:

Vnetd on client :

16:27:14.578 [3588.464] <2> logparams: C:\PROGRA~1\Veritas\NETBAC~1\bin\VNETD.EXE
16:27:14.578 [3588.464] <2> ProcessRequests: .\vnetd.c.288: msg: VNETD ACCEPT FROM 10.195.123.10.3152 TO 10.195.112.192.13724 fd = 540
16:27:14.578 [3588.464] <2> vnet_pop_byte: ..\libvlibs\vnet.c.186: errno: 10054 0x00002746
16:27:14.578 [3588.464] <2> vnet_pop_byte: ..\libvlibs\vnet.c.188: Function failed: 43 0x0000002b
16:27:14.578 [3588.464] <2> vnet_pop_string: ..\libvlibs\vnet.c.268: Function failed: 43 0x0000002b
16:27:14.578 [3588.464] <2> vnet_pop_signed: ..\libvlibs\vnet.c.312: Function failed: 43 0x0000002b
16:27:14.578 [3588.464] <2> vnet_version_accept: .\vnetd.c.1127: Function failed: 43 0x0000002b
16:27:14.578 [3588.464] <2> ProcessRequests: .\vnetd.c.292: version_accept failed: 43 0x0000002b
16:27:14.578 [3588.464] <2> ListenForConnection: .\vnetd.c.594: Function failed: 43 0x0000002b
16:27:14.578 [3588.464] <16> main: Terminating with status 43

bpcd log on client:

16:27:17.468 [3788.404] <2> bpcd main: offset to GMT -28800
16:27:17.484 [3788.404] <2> bpcd main: Got socket for input 560
16:27:17.484 [3788.404] <2> logconnections: BPCD ACCEPT FROM 10.195.123.10.758 TO 10.195.112.192.13782
16:27:17.484 [3788.404] <2> bpcd main: setup_sockopts complete
16:27:17.484 [3788.404] <2> bpcd peer_hostname: Connection from host BACKUP-SERVER (10.195.123.10) port 758
16:27:17.484 [3788.404] <2> bpcd valid_server: comparing backup-server and BACKUP-SERVER
16:27:17.484 [3788.404] <4> bpcd valid_server: hostname comparison succeeded
16:27:17.593 [3788.404] <2> get_short: (1) cannot read (byte 1) from network: An existing connection was forcibly closed by the remote host。
16:27:17.593 [3788.404] <2> bpcd main: output socket port number = 65533
16:27:17.593 [3788.404] <2> bpcd peer_hostname: Connection from host BACKUP-SERVER (10.195.123.10) port 758
16:27:17.593 [3788.404] <2> bpcd main: Peer hostname is BACKUP-SERVER
16:27:17.593 [3788.404] <2> nb_bind_on_port_addr: set socket option SO_EXCLUSIVEADDRUSE
16:27:17.593 [3788.404] <2> bpcd main: Got socket for output 1864, lport = 900
16:27:18.687 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:20.187 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:21.687 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:23.187 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:24.687 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:26.187 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:27.687 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:29.187 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:30.687 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:32.187 [3788.404] <8> bpcd main: connection refused for port 65533, try again
16:27:33.687 [3788.404] <16> bpcd main: Couldn't connect to address 10.195.123.10 port 65533: No connection could be made because the target machine actively refused it.。

 what id reason?

[Andy_Welburn]

Backup or restore fails with status 5/6/21/25 at either the beginning or end of the job
http://www.symantec.com/business/support/index?page=content&id=TECH156471

altho' there may be others....

But can you confirm your hostname resolution? You say your tests are failing, what are the errors?

***EDIT***

These are the "others" which indicate possible network/name resolution:

http://www.symantec.com/business/support/index?page=content&id=TECH56944
http://www.symantec.com/business/support/index?page=content&id=TECH63457

[Will_Restore]

is likely culprit since ping and telnet work ok.  NetBackup is quite picky about forward (name to IP) and reverse (IP to name) name resolution.

[JMP51483]

just in troubleshooting steps.. Please disable all antivirus software / firewall software on the machine. If you disable these ... do you still have the same issues?

Do you use Mcafee EPO in your environment?

[Marianne]

Which NBU version on client?

5.1?

You can see that server is connecting to port 13782 on client. Since NBU 6.0, connection is made on port 13724.
You can also see that the client is trying to connect back on a random port number (65533) instead of port 13724 that is used as from 6.0.

You can force connections on vnetd port (13724) as follows:

Open Host Properties on Master, select Master -> Client Attributes.
If this Client name does not exist in the Client list, add it.
Select Connect Options :
BPCD connect back : VNETD port. 
Daemon connection port : VNETD only.

[kaka_wang]

nbu on client also nbu6.5.5

I try test in my vmware server .

I set firewall setting

but the connect backup port cann't channge.in my env ,the connect backup always port 1.

so how to set a port to connect backup to master server .

[Marianne]

NetBackup server is listening on port 13724 for client connect-back - not port 1.

You client is currently tryin to connect back on random ports (not even port 1).

The minimum NBU port requirement is to have port 13724 open in both directions.

See http://www.symantec.com/docs/TECH136090

[kaka_wang]

------------------ NetBackup bpclntcmd information report ------------------
------------- nbsu diagnostic name and internal procedure used -------------
NBU_bpclntcmd - NBU_get_bpclntcmd_info
------------------------------- Command Used -------------------------------
> "C:\Program Files\Veritas\netbackup\bin\bpclntcmd" -self
gethostname() returned: scmis-qz01-1
host scmis-qz01-1: scmis-qz01-1 at 10.195.112.192 (0xc070c30a)
aliases:
------------------------------- Command Used -------------------------------
> "C:\Program Files\Veritas\netbackup\bin\bpclntcmd" -sv
----------------------------- EXIT STATUS = 23 -----------------------------
------------------------------- Command Used -------------------------------
> "C:\Program Files\Veritas\netbackup\bin\bpclntcmd" -pn
----------------------------- EXIT STATUS = 23 -----------------------------
---------------------------------- STDERR ----------------------------------
expecting response from server backup-server

[Mark_Solutions]

Could you export the HKLM\Software\Veritas\NetBackup|CurrentVersion\Config\ registry keys from the Master and Client, rename them as .txt and attached them to this thread please.

Could you also look on the Master to see if there is a folder named as follows:

<installpath>\veritas\netbackup\db\client\scmis-qz01-1 

If so please paste the contents of the Host_info file on here so that we can have a look further into this

Thanks

[Marianne]

Did you verify that port 13724 is open in both directions between server and client?

Status 23 is probably because of blocked firewall ports.

[kaka_wang]

port 13724 is open on master server and client .

master server command bptestbpcd

C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -verbose -debug -client scmis-qz01-1
16:22:38.109 [3124.6352] <2> bptestbpcd: VERBOSE = 5
16:22:38.125 [3124.6352] <2> read_client: ?
16:22:38.125 [3124.6352] <2> read_client: opendir() failed: scmis-qz01-1: No such file or direct
ory (2)
16:22:38.125 [3124.6352] <2> ConnectToBPCD: db_getCLIENT(scmis-qz01-1) failed: 227
16:22:38.125 [3124.6352] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :qzadmin
16:22:38.125 [3124.6352] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect
_opts2 = 0x01000100
16:22:38.125 [3124.6352] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
16:22:38.125 [3124.6352] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000
028
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000
028
16:22:38.125 [3124.6352] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
16:22:38.125 [3124.6352] <2> vnet_async_connect: vnet_vnetd.c.4035: connect in progress: 0 0x0
0000000
16:22:41.140 [3124.6352] <2> vnet_pop_byte: vnet.c.186: errno: 10054 0x00002746
16:22:41.140 [3124.6352] <2> vnet_pop_byte: vnet.c.188: Function failed: 43 0x0000002b
16:22:41.140 [3124.6352] <2> vnet_pop_string: vnet.c.268: Function failed: 43 0x0000002b
16:22:41.140 [3124.6352] <2> vnet_pop_signed: vnet.c.312: Function failed: 43 0x0000002b
16:22:41.140 [3124.6352] <2> version_connect: vnet_vnetd.c.1817: Function failed: 43 0x0000002
b
16:22:41.140 [3124.6352] <2> do_vnetd_service: vnet_vnetd.c.4409: version_connect failed: 43 0
x0000002b
16:22:41.140 [3124.6352] <2> vnet_async_connect: vnet_vnetd.c.4209: do_vnetd_service failed: 4
3 0x0000002b
16:22:41.140 [3124.6352] <2> vnet_async_connect: vnet_vnetd.c.4035: connect in progress: 1 0x0
0000001
16:22:41.156 [3124.6352] <2> vnet_async_connect: vnet_vnetd.c.4221: in progress connect: 1 0x0
0000001
16:22:41.156 [3124.6352] <2> vnet_async_connect: vnet_vnetd.c.4224: connect: async CONNECT FRO
M 10.195.123.10.884 TO 10.195.112.192.13782 fd = 1772
16:22:41.156 [3124.6352] <2> logconnections: BPCD CONNECT FROM 10.195.123.10.884 TO 10.195.112
.192.13782
16:22:41.156 [3124.6352] <2> vauth_authentication_required: vauth_comm.c.749: no methods for a
ddress: no authentication required
16:22:41.156 [3124.6352] <2> vauth_connector: vauth_comm.c.182: no methods for address: no aut
hentication required
16:22:41.156 [3124.6352] <2> bpcr_authenticate_connection: no authentication required
16:22:41.156 [3124.6352] <2> vnet_vnetd_push_ipaddr: vnet_vnetd.c.1875: sizeof (name.sin_addr.
s_addr): 4 0x00000004
16:22:41.156 [3124.6352] <2> vnet_vnetd_push_ipaddr: vnet_vnetd.c.1884: i: 4 0x00000004
16:22:41.156 [3124.6352] <2> vnet_vnetd_push_ipaddr: vnet_vnetd.c.1895: port: 13724 0x0000359c

16:22:41.156 [3124.6352] <2> vnet_begin_connect_back: vnet_vnetd.c.714: ipc_string: 3745
16:22:44.093 [3124.6352] <2> vnet_pop_byte: vnet.c.186: errno: 10054 0x00002746
16:22:44.093 [3124.6352] <2> vnet_pop_byte: vnet.c.188: Function failed: 43 0x0000002b
16:22:44.093 [3124.6352] <2> vnet_pop_string: vnet.c.268: Function failed: 43 0x0000002b
16:22:44.093 [3124.6352] <2> vnet_pop_signed: vnet.c.312: Function failed: 43 0x0000002b
16:22:44.093 [3124.6352] <2> vnet_pop_status: vnet.c.390: Function failed: 43 0x0000002b
16:22:44.093 [3124.6352] <2> vnet_begin_connect_back: vnet_vnetd.c.723: status: 43 0x0000002b
16:22:44.093 [3124.6352] <2> ConnectToBPCD: bpcd_connect_and_verify(
, scmis-qz01-1) fa
iled: 0
<16>bptestbpcd main: 函数 ConnectToBPCD(scmis-qz01-1) 失败: 25
16:22:44.140 [3124.6352] <16> bptestbpcd main: Function ConnectToBPCD(scmis-qz01-1) failed: 25
<2>bptestbpcd: cannot connect on socket
16:22:44.156 [3124.6352] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
16:22:44.156 [3124.6352] <2> bptestbpcd: EXIT status = 25
无法连接到套接字上

[kaka_wang]

may be client is be-nat ? it ia a reason?

i usr the command pathping from sever to client and from client to server ,find client have more one route path.

like this :

client --> server:

10.195.112.192 --client

10.195.113.*

10.195.116.*

10.195.122.*

10.195.122.* --server

 server-->client

10.195.122.* (server ip)

10.195.122.*

10.195.113.*

10.195.112.192 --client