cancel
Showing results for 
Search instead for 
Did you mean: 

Backup failing with error code 58

Sujay_Kulkarni
Level 2

Master Server Version - 7.5.0.6

Master Server OS - Windows 2003 Enterprise Edition

Client Version - 7.5.0.6

Client OS - Microsoft Windows Server 2008 R2 Standard / 6.1.7601 Service Pack 1 Build 7601

 

bpcd logs attached

1 ACCEPTED SOLUTION

Accepted Solutions

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

All connections attempted were refused by biserver. Please check if any firewall or AV block connections.

View solution in original post

6 REPLIES 6

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

This bpcd file seems like that of master server. Please post bpcd log on client host.
IN addition, run following commands and attach these outputs here.

  • bpclntcmd -self
  • bpclntcmd -ip 10.22.8.141
  • bpclntcmd -ip <IP_of_media_server>
  • bpclntcmd -ip <IP_of_client>
  • bpclntcmd -hn <hostname_of_master>
  • bpclntcmd -hn <hostname_of_media_server>
  • bpclntcmd -hn <hostname_of_client>

Sujay_Kulkarni
Level 2

bpcd logs are from client server itself, below are outputs -

 

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: biserver.au.agrium.com
host biserver.au.agrium.com: BISERVER.au.agrium.com at ::1
host biserver.au.agrium.com: BISERVER.au.agrium.com at 10.22.8.141
aliases:     BISERVER.au.agrium.com     ::1     10.22.8.141

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 10.22.8.141
host 10.22.8.141: 10.22.8.141 at 10.22.8.141
aliases:     10.22.8.141

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 10.21.8.119
host 10.21.8.119: 10.21.8.119 at 10.21.8.119
aliases:     10.21.8.119


C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn svwutmel501
host svwutmel501: svwutmel501 at 10.21.8.143
aliases:     svwutmel501     10.21.8.143

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn svwutmel711
host svwutmel711: svwutmel711 at 10.21.8.119
aliases:     svwutmel711     10.21.8.119

From Media server -

C:\Documents and Settings\kulkarnis>bpclntcmd -hn biserver
host biserver: biserver at 10.22.8.141
aliases:     biserver     10.22.8.141

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Yasuhisa is right - the only connection attempt in this bpcd log is from the host to itself:

BPCD ACCEPT FROM 10.22.8.141.61331 TO 10.22.8.141.13782 fd = 472

 

Have you verified that Windows firewall is disabled on the client?
Or that port 1556 is open in all directions between client and master and media servers?

Please create bpcd log folder on the client and perform this test from the master and all media servers that need to backup this client:

bptestbpcd -client <client-name> -verbose -debug
(Command is in ..netbackup\bin\admincmd)

Please post output of command.

Check bpcd log on client.
If no log is created it means that the connection attempt is not getting to the client.
Probably because of firewall.

If log is created, plese copy to bpcd.txt and upload as File attachment.

*** EDIT ***

You can see that bpclntcmd is unable to resolve ip to hostname.
NBU needs reverse lookup so that IP addresses from master and media servers can be resolved to hostnames and compared with NBU Server list (as can be seen in bpcd log.)

You need to check that reverse lookup is enabled on DNS server or else add hosts entries on the client for client itself as well as master and media servers.

Sujay_Kulkarni
Level 2

Hi Thanks for suggestions. I checked for one of other client which is having same configuration but backups are getting successful fot that even though reverse lookup is not working. however below are the logs for bptestbpcd -client <client-name> -verbose -debug from one of the media server
 

16:27:32.472 [7152.6712] <2> bptestbpcd: VERBOSE = 0
16:27:32.472 [7152.6712] <2> ConnectionCache::connectAndCache: Acquiring new connection for host svwutmel501, query type 223
16:27:32.487 [7152.6712] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:27:32.487 [7152.6712] <2> logconnections: BPDBM CONNECT FROM 10.21.8.119.1618 TO 10.21.8.143.1556 fd = 1744
16:27:32.487 [7152.6712] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
16:27:32.534 [7152.6712] <2> db_CLIENTsend: reset client protocol version from 0 to 8
16:27:32.706 [7152.6712] <2> db_getCLIENT: db_CLIENTreceive: no entity was found 227
16:28:02.707 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:28:03.629 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:28:33.630 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:28:34.630 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:28:44.536 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:29:14.537 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:29:16.537 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:29:25.459 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:29:55.460 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:29:59.460 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:30:06.460 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:30:36.461 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:30:44.461 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:30:47.367 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:31:08.384 [7152.6712] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 10060 0x274c
16:31:08.384 [7152.6712] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO biserver 10.22.8.141 bpcd VIA pbx
        status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO biserver 10.22.8.141 bpcd VIA vnetd
        status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO biserver 10.22.8.141 bpcd
16:31:08.384 [7152.6712] <8> vnet_connect_to_bpcd: [vnet_connect.c:279] connect_to_service() failed 18 0x12
16:31:08.384 [7152.6712] <2> local_bpcr_connect: Can't connect to client biserver
16:31:08.384 [7152.6712] <2> ConnectToBPCD: bpcd_connect_and_verify(biserver, biserver) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(biserver) failed: 25
16:31:08.384 [7152.6712] <16> bptestbpcd main: Function ConnectToBPCD(biserver) failed: 25
<2>bptestbpcd: cannot connect on socket
16:31:08.384 [7152.6712] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
16:31:08.384 [7152.6712] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

 

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

All connections attempted were refused by biserver. Please check if any firewall or AV block connections.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If you check bpcd log on working clients, you will see that they can resolve media server IP address to a hostname that appears in the Server list.

Two problems on this client: 

1. Firewall blocking all ports - either Windows firewall or company firewall. Or even AV as Yasuhisa said.

2. Reverse lookup. Client must be able to resolve incoming IP address from media server to hostname that appears in Server list.