SQL backup failure
Created: 31 Jan 2013 | 6 comments
Hi Guys
i have a windows client .Netbackup SQL backup configured on it .but it fails . netbackup filesystem backup goes fine on it.
bpclntcmd host to ip , ip to hostname resolution is successful.
C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -check_vxss
cannot connect on socket
dbclient log from client server :
10:52:42.120 [5504.3844] <4> VxBSAInit: Veritas NetBackup XBSA Interface - 7.1 0
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_API
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - returning -
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_FEATURE_ID
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - returning - <FEATURE_ID>
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - returning - masterserver.net
10:52:42.120 [5504.3844] <4> bsa_checkFeatureId: INF - entering bsa_checkFeatureId
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
10:52:42.120 [5504.3844] <4> VxBSAGetEnv: INF - returning - masterserver.net
10:52:42.120 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6646: 0: fopen() failed: 2 0x00000002
10:52:42.120 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6647: 0: fopen() failed: C:\Program Files\Veritas\NetBackup\var\host_cache\1ea\fbd1c3ea+veritas_pbx,1,0,2,1,0+masterserver.net.txt
10:52:42.120 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6646: 0: fopen() failed: 2 0x00000002
10:52:42.120 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6647: 0: fopen() failed: C:\Program Files\Veritas\NetBackup\var\host_cache\18a\68c04b8a+0,1,2,0,1,0+13.145.126.147.txt
10:52:42.135 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6646: 0: fopen() failed: 2 0x00000002
10:52:42.135 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6647: 0: fopen() failed: C:\Program Files\Veritas\NetBackup\var\host_cache\1ea\fbd1c3ea+vnetd,1,0,2,1,0+masterserver.net.txt
10:52:42.135 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6646: 0: fopen() failed: 2 0x00000002
10:52:42.135 [5504.3844] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6647: 0: fopen() failed: C:\Program Files\Veritas\NetBackup\var\host_cache\1ea\fbd1c3ea+bprd,1,0,2,1,0+masterserver.net.txt
10:52:52.151 [5504.3844] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.666: pbxSetAddrEx/pbxConnectEx return error 121:The semaphore timeout period has expired.
10:52:52.151 [5504.3844] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1718: 0: vnet_pbxConnect() failed: 18 0x00000012
10:52:52.151 [5504.3844] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1719: 0: save_errno: 121 0x00000079
10:52:52.151 [5504.3844] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1720: 0: use_vnetd: 0 0x00000000
10:52:52.151 [5504.3844] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1721: 0: cr->vcr_service: bprd
10:52:52.151 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1353: 0: do_service failed: 18 0x00000012
10:53:13.120 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:53:22.979 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:53:45.979 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:53:55.073 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:54:17.995 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:54:37.995 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:54:48.980 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:55:10.980 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:55:20.074 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:55:40.980 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:55:40.980 [5504.3844] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
10:55:40.980 [5504.3844] <2> vnet_connect_to_service: ../../libvlibs/vnet_connect.c.174: 0: connect_to_service() failed: 18 0x00000012
10:55:40.980 [5504.3844] <2> bprd_connect: vnet_connect_to_service(masterserver.net) failed: 18
10:55:40.980 [5504.3844] <2> bprd_get_features: bprd_connect(masterserver.net) failed, cannot connect on socket (25)
10:55:40.980 [5504.3844] <8> bsa_checkFeatureId: bprd_get_features() failed, retrying
10:56:10.996 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:56:11.965 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:56:21.934 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:56:52.934 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:56:53.918 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:57:03.856 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:57:35.856 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:57:49.856 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:57:49.856 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:58:00.903 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:58:30.903 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:58:31.778 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:58:42.044 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:59:12.044 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:59:14.044 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:59:22.872 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:59:22.872 [5504.3844] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
10:59:22.872 [5504.3844] <2> vnet_connect_to_service: ../../libvlibs/vnet_connect.c.174: 0: connect_to_service() failed: 18 0x00000012
10:59:22.872 [5504.3844] <2> bprd_connect: vnet_connect_to_service(masterserver.net) failed: 18
10:59:22.872 [5504.3844] <2> bprd_get_features: bprd_connect(masterserver.net) failed, cannot connect on socket (25)
10:59:22.872 [5504.3844] <8> bsa_checkFeatureId: bprd_get_features() failed, retrying
10:59:52.872 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
10:59:53.857 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:00:03.826 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:00:34.826 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:00:35.810 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:00:45.763 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:01:17.764 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:01:31.764 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:01:31.764 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:01:42.795 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:02:12.795 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:02:13.670 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:02:23.733 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:02:53.733 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:02:55.733 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:03:04.670 [5504.3844] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 10060 0x0000274c
11:03:04.670 [5504.3844] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
11:03:04.670 [5504.3844] <2> vnet_connect_to_service: ../../libvlibs/vnet_connect.c.174: 0: connect_to_service() failed: 18 0x00000012
11:03:04.670 [5504.3844] <2> bprd_connect: vnet_connect_to_service(masterserver.net) failed: 18
11:03:04.670 [5504.3844] <2> bprd_get_features: bprd_connect(masterserver.net) failed, cannot connect on socket (25)
11:03:04.670 [5504.3844] <16> bsa_checkFeatureId: unable to check if feature <33> is licensed
11:03:04.670 [5504.3844] <16> bsa_checkFeatureId: Server exit status = 25: cannot connect on socket
11:03:04.670 [5504.3844] <16> VxBSAInit: ERR - The license for the requested feature is not available.
11:03:04.670 [5504.3844] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_DEBUGFD
11:03:04.670 [5504.3844] <4> VxBSAGetEnv: INF - returning -
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
Comms for filesystem backup works different. No comms is initiated from client directly to master server. This is needed for database backups.
You can see in dbclient log that client is attempting to connect to bprd (via pbx) to the master server, but cannot do so.
Please ensure successful forward and reverse lookup between client and server (use 'bpclntcmd -hn <hostname>' and 'bpclntcmd -ip <IP>' in both directions) and also ensure that PBX (port 1556) is open in both directions between master and client.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
pbx port open in both directions. bpclntcmd -hn and bpclntcmd -ip done from master and client. output is fine.
Check bprd log on master server for incoming request from client.
See how master is resolving client's IP to hostname. Then check if this resolved client name matches the client name in the policy.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
What version of Netbackup are you running ? I remember there being an issue back in 6.5.6 ( which is no longer supported ) In addtion to the bprd, please upload vnetd
NBU version is 7.1.0.2
Check if this helps
http://www.symantec.com/docs/TECH43388
http://www.symantec.com/docs/TECH44647
Cheers !!!
EV Outlook Client Add-ins
Would you like to reply?
Login or Register to post your comment.