Video Screencast Help

Netbackup bpend_notify results to job details

Created: 01 Feb 2013 • Updated: 21 Apr 2013 | 4 comments
jpajula's picture
This issue has been solved. See solution.

Is it possible to get any return code back to originating backup job from bpend_notify.bat? It would be nice to know if bpend_notify.bat exits with any other return code than 0.

This came out when trying to create Notes DAOS backups which is not yet (ever?) supported by Netbackup. So we could first make online backup and immediately after that, launch filesystem backup for DAOS with bpbackup command. I have tested this only with filesystem backup and it seems to work, but no error is logged even if the bpend_notify.bat fails. So far it is not possible to create alert policy in OpsCenter if the job is completely skipped.

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

CRZ's picture

This is way out of my level of expertise, but the only thing I can think of is to use bpend_notify.bat as a wrapper to a script which REALLY does what you want it to, and then grab the return code from your wrapped bat and decide how you want bpend_notify to deal with it.  (I THINK this would work.)

Google threw me to the always great Stack Overflow for an idea of what your wrapper might look like:

Good luck! | APPLBN | 761LBN

Mark_Solutions's picture

bpend_notify.bat has the variable %5 = Status of backup which would pipe that out

For parent jobs it would need to come from the Master Server using parent_start_notify.bat  with uses the same variable

Not sure if that was what you were looking for?

Authorised Symantec Consultant . Expert Partner.

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Dyneshia's picture  -
DOCUMENTATION: Email Notifications Settings and Their Behaviors

DOCUMENTATION: How to configure email notification and the different methods to email backup exit statuses from a UNIX master in NetBackup  - How to configure Symantec NetBackup (tm) to send email notification only when a job fails

Stumpr2's picture

If you want to compare what should have run against what actually ran then you could use nbpemreq -predict bounced against bpdbjobs

VERITAS ain't it the truth?