Backup failing with error code 23
Hi Team, One windows client backup is getting failed with error code 23 from today. Below is the bptestbpcd output from master. Tried adding master server hostname and IP on client machine and cli...
Forum Discussion
Have you checked if NetBackup Client Services are running on the client?
If so, create bpcd log folder on the client (under ...\netbacup\logs) and run bptestbpcd again.
Check bpcd log on the client for errors.
Hi Marianne,
Yes, the netbackup client service is running.
C:\Program Files\Veritas\NetBackup\bin>bpps
* MISPW3206 6/27/18 08:25:01.768
COMMAND PID LOAD TIME MEM START
vnetd 7108 0.000% 0.078 8.7M 6/27/18 07:32:44.245
bpinetd 7220 0.000% 5.070 11M 6/27/18 07:32:44.291
mtstrmd 5024 0.000% 0.046 7.3M 6/27/18 07:32:49.112
vnetd 1864 0.000% 0.046 8.2M 6/27/18 08:24:24.359
bpps 7724 0.000% 0.265 8.2M 6/27/18 08:25:00.489
bpcd log
==================
08:24:24.390 [1988.2044] <2> setup_debug_log: switched debug log file for bpcd
08:24:24.390 [1988.2044] <4> bpcd main: VERBOSE=0, BPCD VERBOSE=0 Timestamp=1530098791
08:24:24.390 [1988.2044] <2> logparams: bpcd
08:24:24.390 [1988.2044] <2> bpcd main: Got socket for input 464
08:24:24.390 [1988.2044] <2> process_requests: offset to GMT 18000
08:24:24.406 [1988.2044] <2> logconnections: BPCD ACCEPT FROM 10.128.44.226.60917 TO 10.128.74.45.13724 fd = 464
08:24:24.406 [1988.2044] <2> process_requests: setup_sockopts complete
08:24:24.437 [1988.2044] <2> bpcd peer_hostname: Connection from host to1pw3243.statestr.com (10.128.44.226) port 60917
08:24:24.546 [1988.2044] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:24:24.577 [1988.2044] <8> do_pbx_service: [vnet_connect.c:2186] via PBX VNETD CONNECT FROM 10.128.74.45.49968 TO 10.128.44.226.1556 fd = 496
08:24:24.593 [1988.2044] <8> vnet_vnetd_get_security_info: [vnet_vnetd.c:2800] VN_REQUEST_GET_SECURITY_INFO 9 0x9
08:24:25.233 [1988.2044] <8> vnet_vnetd_disconnect: [vnet_vnetd.c:198] VN_REQUEST_DISCONNECT 1 0x1
08:24:25.233 [1988.2044] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1733] in failed file cache ERR=11001 NAME=eb60574b-b7fd-4828-a4a6-7b04cdd5d9e1 SVC=NULL
08:24:25.233 [1988.2044] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1402] vnet_cached_getaddrinfo_and_update() failed 6 0x6
08:24:25.233 [1988.2044] <8> vnet_same_host_and_update: [vnet_addrinfo.c:3013] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME1=eb60574b-b7fd-4828-a4a6-7b04cdd5d9e1
08:24:25.233 [1988.2044] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1733] in failed file cache ERR=11001 NAME=keystore SVC=NULL
08:24:25.233 [1988.2044] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1402] vnet_cached_getaddrinfo_and_update() failed 6 0x6
08:24:25.233 [1988.2044] <8> vnet_same_host_and_update: [vnet_addrinfo.c:3013] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME1=keystore
08:24:25.279 [1988.2044] <16> VssImportCredential: (../../libVnbat/vss_auth.cpp,3299): Cred file open FAILED
08:24:25.279 [1988.2044] <8> vnet_setup_vxss_socket: [vnet_vxss_helper.c:189] vnet_vxss_import_credential() failed 36 0x24
08:24:25.279 [1988.2044] <16> process_requests: vnet_setup_vxss_socket(to1pw3243.statestr.com) failed: 36
What version of netbackup are you running ?
Try on the client running bpclntcmd -clear_host_cache
According to the logs shown, it looks like a name resolution issue
Hi Nicholai,
Tried clearing host cache but didn't worked.
NBU version on master is 8.1.1 and on client is 8.0
Master and media are same.
The Status 36 error that I see in bpcd log is new to me.
08:24:25.279 [1988.2044] <16> process_requests: vnet_setup_vxss_socket(to1pw3243.statestr.com) failed: 36
Status Code Ref Guide says this about status 36:
NetBackup status code: 36
Message: failed trying to allocate memory
Explanation: Allocation of system memory failed. This error occurs when an insufficient system memory is available. The system may be overloaded with too many processes and it does not have enough physical and virtual memory.
Recommended Action: Free up memory by terminating any unneeded processes that consume a lot of memory. Add more swap space or physical memory.
Can you please check if this is relevant here?
Hi Marianne,
Have informed windows team to have a look into memory.
