Forum Discussion

Bhaskar_Regmi's avatar
17 years ago

bpbrm error - Cannot execute cmd on client

Backup is failing with status client/server handshaking failed. As the master server and client are in the same subnet, it's not firewall issue. bpbrm log on master server is showing I/O error.

 

10:48:34.390 [5213] <2> bpcr_authenticate_connection: no authentication required
10:48:34.391 [5213] <2> nb_bind_on_port_addr: bound to port 3172
10:48:34.393 [5213] <2> bpbrm start_bpcd: DATA_SOCK from bpcr = 8
10:48:34.393 [5213] <2> bpbrm start_bpcd: NAME_SOCK from bpcr = 11
10:48:34.393 [5213] <2> bpbrm handle_backup: calling bpcr_get_socket_rqst3.
10:48:34.393 [5213] <2> bpbrm handle_backup: bpbrm.c.12969: media_port: 2989 2989 0x00000bad
10:48:34.393 [5213] <2> bpbrm handle_backup: bpbrm.c.12970: mpx_ipc:
10:48:34.395 [5213] <2> get_long: (2) premature end of file (byte 1)
10:48:34.396 [5213] <2> bpcr_check_for_use_ofb_support: bpcd version unknown
10:48:34.396 [5213] <2> get_short: (2) premature end of file (byte 1)
10:48:34.396 [5213] <2> readclientstatus: bpcr short int read failed
10:48:34.396 [5213] <2> readclientstatus: error 5 - I/O error

 

What can be causing the problem? Client server communication looks fine.

  • Could be lots of things. A very good check is with bpclntcmd, using the -self, -server <master server> options from both client and master server. You will usually find that one of the options in a particular direction does not resolve. Also check hosts file (and if you have DNS temporarily rename the hosts file on the Master server to run a quick test backup)

     


    E:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -?
    bpclntcmd: unrecognized option -?
    bpclntcmd: -sv
    bpclntcmd: -pn
    bpclntcmd: -self
    bpclntcmd: -hn <hostname>
    bpclntcmd: -server <NBU master>
    bpclntcmd: -ip <ipaddress>
    bpclntcmd: -gethostname
    bpclntcmd: -is_local_host <hostname>
    bpclntcmd: -check_vxss
    bpclntcmd: -check_vxss_with_host <hostname>
    bpclntcmd: -get_pbx_port [<hostname>]
    bpclntcmd: -get_remote_host_version <hostname>
    bpclntcmd: -get_local_client_patch_version
    bpclntcmd: -get_local_server_patch_version
    bpclntcmd: -sanclient <0|1>

  • Could be lots of things. A very good check is with bpclntcmd, using the -self, -server <master server> options from both client and master server. You will usually find that one of the options in a particular direction does not resolve. Also check hosts file (and if you have DNS temporarily rename the hosts file on the Master server to run a quick test backup)

     


    E:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -?
    bpclntcmd: unrecognized option -?
    bpclntcmd: -sv
    bpclntcmd: -pn
    bpclntcmd: -self
    bpclntcmd: -hn <hostname>
    bpclntcmd: -server <NBU master>
    bpclntcmd: -ip <ipaddress>
    bpclntcmd: -gethostname
    bpclntcmd: -is_local_host <hostname>
    bpclntcmd: -check_vxss
    bpclntcmd: -check_vxss_with_host <hostname>
    bpclntcmd: -get_pbx_port [<hostname>]
    bpclntcmd: -get_remote_host_version <hostname>
    bpclntcmd: -get_local_client_patch_version
    bpclntcmd: -get_local_server_patch_version
    bpclntcmd: -sanclient <0|1>

  • You are right, it was a name resolution problem on client site. Thanks for the quick solution.