bpend_notify script design

[somesh_p]

I have bpend_notify script for solaris client.  I am setting following variable at the begining of the script.

BKUP_CLIENT=${1}

POLICY_ID=${2}

SCHED_NAME=${3}

SCHED_TYPE=${4}

BKUP_STAT=${5}

But, when the backup fails with error code  252 (no space left on target device), I am seeing BKUP_STAT variable assigned with 150. Why is it so?  Is 150 BACKUP status common for all backup failures in bpend_notify script. Can any one explain how to export accurate backup failure code into bpend_notify script for further processing ??

[Marianne · Accepted solution]

Your bpend status shows the status on the client, not the server.  So, the parent-process on the media server sent a kill/cancel signal to bpbkar on the client when the media server encountered disk full.

As per NBU Admin Guide II : 

exitstatus:

Specifies the exit code from bpbkar. The status is the client status

and does not indicate that the backup is complete and successful.

The client can display a status 0 when, due to a failure on the server,

the All Log Entries report displays a status 84.

If you want backup status notification, you have to configure server-side notification.
See http://www.symantec.com/docs/TECH64984