02-29-2012 02:55 AM
Dears,
After upgrading Netbackup to 7.1.0.3 backup_exit_notify no more send Email notification,
Troubleshooting Steps using command prompt
find attchment
02-29-2012 11:04 AM
I think your script IS running but it's not behaving the way you're expecting.
In 7.1.0.3, an eighth parameter was added to backup_exit_notify (primary jobID). (This change was also made in 7.5; it was backported into 7.1.0.3).
I think that's tripping you up right here:
@if "%7" == "" goto BadParams @if "%8" == "" goto GoodParams
%8 is no longer blank so with %7 ALSO not blank, you're not going to BadParams OR GoodParams.
You'll need to tweak your conditionals and it should start behaving as you expect.
This change was buried in the 7.1.0.3 Release Notes on page 74:
Etrack Incident: 2589153
■ Associated Primary Etrack: 2588134
■ TITAN cases: 415-519-972
■ Contained in: NBLU_7.1.0.3.UNIX NBLU_7.1.0.3.WIN NB_7.1.0.3
NB_7.1.0.3.winnt.IA64 NB_7.1.0.3.winnt.x64 NB_7.1.0.3.winnt.x86
NB_CLT_7.1.0.3
■ Description:
The PrimaryJobId was added to the parameter list of the backup_exit_notify
callout. The callout on UNIX and Windows was modified to expect this new
parameter, and to allow future parameter additions without error. Parameters
are always added to the end of the list.
■ Additional Notes:
The installer overwrote the existing backup_exit_notify callout, so a callout
needed to be backed up if it had been customized.Acustomized callout needed
to be reviewed to be sure it did not fail when it was passed the new JobId
parameter.