STATUS CODE: 5, 49 A restore fails with a Status 5 in the GUI and a Status 49 "Client did not start" is received in the logs.

Overview:
Restore jobs queue and do not goactive.  These eventually fail with a Status 5 in the Activitymonitor.  A closer look at the bpbrm log will show the job failed witha Status 49 (client did not start).  This can be caused when the tar binary has been removed on theclient.


Troubleshooting:
Verify the tar binary is installed on theclient.  If the tar binary ismissing, the following error will be displayed:
#ls -l/usr/openv/netbackup/bin/tar
/usr/openv/netbackup/bin/tar:No such file or directory


Media Server LogFiles:
The /usr/openv/netbackup/logs/bpbrm/log.<date> willshow the child bpbrm process failingwith an error:
17:54:24.673 [6835] <2>bpbrm handle_restore: received bpcd successmessage
17:54:24.680 [6835] <2>bpbrm readline: EOF detected on NAMEsocket
17:54:24.680 [6835]<16> bpbrm handle_restore: client <hostname> didn'tstart

The corresponding bpbrm parent process then failswith a status 49.
17:54:24.960 [6822] <2>bpbrm brm_sigcld: bpbrm child 6835 exit_status = 49, signal_status =0
17:54:24.960 [6822] <2> bpbrmbrm_sigcld: child 6835 exited with status 49: client did notstart


Resolution:
To reinstall the clientbinaries use the update_clients command.  This will reload any binaries that are missing or that may becorrupt.

1) Create a /tmp/client_list file with a list of clientsto update and add the entry.
Solaris Solaris9<hostname>
Where Solaris is the hardware platform, Solaris9 is the OS version and <hostname> is the client hostnameto update.

2) Then run the update_clients command to reinstall theclient software:
#/usr/openv/netbackup/bin
#./update_clients -ForceInstall -ClientList/tmp/client_list

As a workaround, the tar binary can be copied from a workingclient that is running the same Operating System and hardware platform as thefailing client.  Once the tar binary is copied to the nonworking client, verify the correct ownership andpermissions are set properly.  

# chmod555 tar
# chown roottar
# chgrp bintar
# ls -latar
-r-xr-xr-x   1root  bin   462028 May 14 13:34tar

Note:  The exact size of the tar binary will vary depending on theNetBackup version, operating system version and hardware platform.