Status code 73 on Solaris server - bpstart_notify failed
Yellow all...
Setup:
1. NBU 5.0 (don't ask...)
2. SunOS fileinfra1 5.9 Generic_122300-51 sun4u sparc SUNW,Sun-Fire-V240
Problems:
Differential or full backups fail invariably with the same status code 73 for this particular machine:
1127444 Backup Done 73 solaris_dyn_backup_fileinfra1 diff fileinfra1mgt1 fileinfra1mgt1 09/05/11 14:04:18 000:00:20 09/05/11 14:04:38
1126991 Backup Done 73 solaris_dyn_backup_fileinfra1 full fileinfra1mgt1 fileinfra1mgt1 09/04/11 12:09:12 000:00:18 09/04/11 12:09:30
From the logs:
1315570102 1 4 4 backup34_1 1129315 1129314 0 fileinfra1mgt1 bpsched added backup job (jobid=1129315) for client fileinfra1mgt1, policy solaris_dyn_backup_fileinfra1, schedule diff part 1 to NetBackup scheduler work queue
1315570105 1 4 4 backup34_1 1129315 1129314 0 fileinfra1mgt1 bpsched started backup job for client fileinfra1mgt1, policy solaris_dyn_backup_fileinfra1, schedule diff on storage unit fileinfra1mgt1-hcart2-robot-tld-0
1315570107 1 4 4 backup34_1 1129315 1129314 0 fileinfra1mgt1 bpsched client fileinfra1mgt1 handling path /data/files
1315570112 1 4 16 fileinfra1mgt1 1129315 1129314 0 fileinfra1mgt1 bpbrm from client fileinfra1mgt1: ERR - bpstart_notify returned 1
1315570112 1 4 16 fileinfra1mgt1 1129315 1129314 0 fileinfra1mgt1 bpbrm client fileinfra1mgt1 EXIT STATUS = 73: bpstart_notify failed
1315570123 1 4 16 fileinfra1mgt1 1129315 1129314 0 fileinfra1mgt1 bpsched suspending further backup attempts for client fileinfra1mgt1, policy solaris_dyn_backup_fileinfra1, schedule diff because it has exceeded the configured number of tries
1315570123 1 68 4 fileinfra1mgt1 1129315 1129314 0 fileinfra1mgt1 bpsched CLIENT fileinfra1mgt1 POLICY solaris_dyn_backup_fileinfra1 SCHED diff EXIT STATUS 73 (bpstart_notify failed)
1315570123 1 4 16 fileinfra1mgt1 1129315 1129314 0 fileinfra1mgt1 bpsched backup of client fileinfra1mgt1 exited with status 73 (bpstart_notify failed)
If I try to run the script from the host, this is what the output file tells me:
root@fileinfra1 # more /usr/openv/netbackup/bin/BPSTART_CALLED
Fri Sep 9 14:08:31 MEST 2011 differential incremental backup started on fileinfra1mgt1 - policy solaris_dyn_backup_fileinfra1 schedule diff
I tried restarting the job (resulted in 196...) or directly a bpbackup -i, but to no avail (resulted in 73 again...).
This is the script from the pesky host:
#! /bin/sh
# $Header: bpstart_notify.sh,v 1.3 2003/08/13 14:11:55 $
#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2003 VERITAS Software Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
#
# bpstart_notify.sh
#
# This script is called by NetBackup when bpbkar is started up on the client
# to do a backup or archive.
#
# This script:
# receives 4 parameters: CLIENTNAME POLICYNAME SCHEDNAME SCHEDTYPE
# must be executable by the root user
# should exit with 0 upon successful completion
#
# If this script will not complete within a few seconds, you should set
# the BPSTART_TIMEOUT in the /usr/openv/netbackup/bp.conf file on the server.
# You should also be aware that the time taken by this script will delay
# the initiation of other client's backups.
#
# This script should be installed with mode 555 so that user directed
# backups and archives will be able to execute this script.
#
# CAUTION: writing anything to stdout or stderr will cause backup problems
#
# --------------------------------------------------------------------
# main script starts here
# --------------------------------------------------------------------
umask 022
if [ "$#" -ne 4 ]
then
exit 1
fi
if [ "$4" = "FULL" -o "$4" = "INCR" -o "$4" = "CINC" ]
then
OUTF=/usr/openv/netbackup/bin/BPSTART_CALLED
# You may want to delete the output file elsewhere in order to
# accumulate successful backup information.
# If so, comment out the following 4 lines.
if [ -s $OUTF ]
then
/bin/rm -rf $OUTF
fi
if [ ! -f $OUTF ]
then
touch $OUTF
fi
case "$4"
in
"FULL")
echo `date` full backup started on $1 - policy $2 schedule $3 >> $OUTF
;;
"INCR")
echo `date` differential incremental backup started on $1 - policy $2 schedule $3 >> $OUTF
;;
"CINC")
echo `date` cumulative incremental backup started on $1 - policy $2 schedule $3 >> $OUTF
;;
esac
#
# might want to mail this info to someone
#
# cat $OUTF | mail -s "NetBackup backup started" someone_who_cares
#
# CAUTION: some platforms do not allow the -s parameter on mail
#
fi
exit 0
I've already been through the documentation for NBU 5.0 and the one referring to scripts, but it doesn't help me much. I've compared this script on fileinfra1mgt1 with the one found on its clustered partner (fileinfra2mgt1, whose backups run june fine) and it's the same.
HULP!
Seems it was a matter of naming of the policy... I've copied the policy to a new name, added the path to the files that were backed up by the original policy to the new one and then ran the job. It ran successfully, in both full and diff schedules. I have no other explanation for the issue than the fact that the name of the original backup policy was somehow messed up.