The bpend_notify inherently is weak in the sense that it doesn't
care if the backup job failed with any media error, it exit
status might be zero.  You have two options to do

        - Before netbackup starts the next attempt after a
          failed backup, verify the status of last backup that
          was done.  If it is > 1, then definitely it failed.
          Run whatever the cleanup you have to conditionally
          within bpstart_.

        - Try backup_exit_notify on the master, if you do not
          want the notification for every server, only put
          the hosts you desire in the script.  This script
          gets the actual backup failure code, note not the
          exit status as believed by client side bpbkar.  Based
          on this, you can also manipulate the bpstart.  Not
          very straight forward, still doable.

-ravi

On Thu, 3 May 2001 TWGIBBAR AT up DOT com wrote:

>We have a situation where were using home grown built oracle scripts for
>hot database backups.  Everything works just great with the bpstart and
>bpend scripts unless the job fails with a media or time-out error.  The
>bpend doesn't run to clean things up before the job retries and reruns the
>bpstart script.  This causes errors to pop up in the alert log because the
>tables are already marked for backup and also causes issues when it
>completes because everything isn't always properly cleaned up.  I guess my
>question is, how do I ensure the bpend script runs if the jobs fails after
>the bpstart has already ran?  I hope this mumble jumble makes sense to
>someone.
>
>Thanks,
>Terry
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>