STATUS CODE 26: Backup attempts failing with NetBackup Status Code 26 (client/server handshaking failed).

Article: 100017978
Last Published: 2018-10-08
Ratings: 0 2
Product(s): NetBackup & Alta Data Protection

Problem

Backup attempts failing with NetBackup Status Code 26 (client/server handshaking failed).

 

Error Message

In the media server's bptm log file, the following messages are observed:

16:56:09.039 [2292.980] <2> emmlib_initialize: (-) Connection attempt #<0>
16:56:09.039 [2292.980] <2> emmlib_initializeEx: (-) Connecting to the Server <server_name> Port <1556>, App <dbstunitq> OrbOpt <No extra otions>
16:56:09.055 [2292.980] <2> VssGetFQDNHostName: vss_auth.cpp.3992: Function: VssGetFQD NHostName. Search name
16:56:09.055 [2292.980] <2> VssInit: vss_auth.cpp.681: Function: VssInit. Using Cached  entries FALSE
16:56:09.055 [2292.980] <2> Human Message: Optional VxSS libraries not initialized.
16:56:09.055 [2292.980] <2> VssCleanUp: vss_auth.cpp.816: Function: VssCleanUp result:  21
16:56:09.070 [2292.980] <2> emmlib_initializeEx: (-) Setting request timeout to <1800> sec
16:56:13.617 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.348: Function failed: 6 0x00000006
16:56:13.617 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.348: Function failed: 6 0x00000006
16:56:18.164 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.348: Function failed: 6 0x00000006
16:56:18.164 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.348: Function failed: 6 0x00000006
16:56:22.726 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.287: Function fail
...(snip)...
16:56:54.507 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.287: Function failed: 5 0x00000005
16:56:54.523 [2292.980] <2> vnet_cached_gethostbyname: vnet_hosts.c.287: Function failed: 5 0x00000005
16:56:54.538 [2292.980] <2> emmlib_GetStorageUnit: (0)

 

Cause

Use of the bpclntcmd -hn <server_name> command (correct usage of the command outlined in KB article 100017942, found below in the Related Documents section) indicates one of the servers in the media server's bp.conf file is not correctly configured within the environment's name resolution setup.

Troubleshooting:
Enable the bptm log file on media server and review the media server's bp.conf file. Confirm the bpclntcmd -hn <server_name> command returns successfully for all SERVER= entries in the media server's bp.conf file.

 

Solution

After removing the problem SERVER= line from the bp.conf file, the backup completes successfully.

 

Was this content helpful?