NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 2034

NetBackup status code : 2034
HOWTO104862 | 2014-11-20
How To | CMS-XML

netbackup 6.0 bpbrm Exit: client backup EXIT STATUS 41 | Symantec Connect

netbackup 6.0 bpbrm Exit: client backup EXIT STATUS 41 tail of bpbrm log : 20:28:35.969 [25966] <2> vnet_vnetd_service_socket: vnet_vnetd.c. 2034 : vn_request_service_socket: 6 0x00000006 20:28:35.969 [25966] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bpdbm
Connect Forums | HTML

Solaris 10u9. Unable to connect new client: Status 24/25 | Symantec Connect

Solaris 10u9. Unable to connect new client: Status 24/25 13:10:53.504 [3545] <2> vnet_vnetd_service_socket: vnet_vnetd.c. 2034 : vn_request_service_socket: 6 0x00000006 13:10:53.505 [3545] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bpcd
Connect Forums | HTML

RMAN Backup completed without generating child stream or sometime failing with error code 6 | Symantec Connect

23:54:28.050 [20313] <2> vnet_cached_gethostbyname: vnet_hosts.c.301: found host in cache: hqub5500 23:54:28.067 [20313] <2> vnet_vnetd_service_socket: vnet_vnetd.c. 2034 : vn_request_service_socket: 6 0x00000006 23:54:28.067 [20313] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bprd
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:37:00.067 [5472.4344] <2> logconnections: BPDBM CONNECT FROM 10.239.51.107. 2034 TO 10.239.53.31.1556 fd = 12128
Connect Forums | HTML

Status Code Chart

2033 2034 2035
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Exit status codes 14, 40 and 41 are seen on the Windows client and Media Server

17:00:59.334 [3872.4236] 2 vnet_vnetd_service_socket: vnet_vnetd.c. 2034 : vn_request_service_socket: 6 0x00000006 17:00:59.584 [3872.4236] 2 logconnections: BPDBM CONNECT FROM 10.180.12.12.4453 TO 10.180.32.24.13724 17:00:59.990 [3872.4236] 2 bpbrm main: client big-server EXIT STATUS = 14: file write failed
TECH7963 | 2010-01-14
Technical Solutions | CMS-XML

Exit Status: 48 (client hostname could not be found) | Symantec Connect

08:56:02.271 [3412.752] <8> do_pbx_service: [vnet_connect.c: 2034 ] vnet_pbxconnec
Connect Forums | HTML

NetBackup messages

retry the allocation request later See NetBackup status code : 2034 robot already exists
HOWTO103773 | 2014-11-20
How To | CMS-XML

Restore Issue on Ubuntu 10.04 64 bit client running 6.5.4 | Symantec Connect

Restore Issue on Ubuntu 10.04 64 bit client running 6.5.4 10:42:27.240 [852.6660] <2> vnet_cached_gethostbyname: vnet_hosts.c.301: found host in cache: sdutility-02.divxnetworks.com 10:42:27.255 [852.6660] <2> vnet_vnetd_service_socket: vnet_vnetd.c. 2034 : vn_request_service_socket: 6 0x00000006 10:42:27.255 [852.6660] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bpcd
Connect Forums | HTML

RMAN Backup failing after backup "begin writing" | Symantec Connect

08:06:14.463 [42860712] <2> vnet_pbxconnect: ../../libvlibs/vnet_pbx.c.666: pbxSetAddrEx/pbxConnectEx return error 73:Connection reset by peer 08:06:14.463 [42860712] <8> do_pbx_service: [vnet_connect.c: 2034 ] vnet_pbxconnect() failed 18 0x12 08:06:14.463 [42860712] <8> do_pbx_service: [vnet_connect.c:2035] save_errno 73 0x49
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?