There is a naming convention you need to follow to use bpstart and exit notify scripts.
To create a bpstart_notify script for a specific policy or policy and schedule
combination, create script files with a .policyname or .policyname.schedulename suffix. The
following are two examples of script names for a policy named production that has a
schedule named fulls:
/usr/openv/netbackup/bin/bpstart_notify.production
/usr/openv/netbackup/bin/bpstart_notify.production.fulls
The first script affects all scheduled backups in the policy named production. The second
script affects scheduled backups in the policy named production only when the schedule
is named fulls.
If the /usr/openv/netbackup/bin/bpstart_notify script exists, it runs in the
foreground and the bpbkar process on the client waits for it to complete before
continuing. Any commands in the script that do not end with an & character run serially.
The server expects the client to respond with a continue message within the period of
time specified by the NetBackup BPSTART_TIMEOUT option on the server.
The default for BPSTART_TIMEOUT is 300. If the script needs more time than 300 seconds, increase the value to allow more time.
Caution - If you use either the bpstart_notify or bpend_notify scripts, do not
include commands that write to stdout. If you do, NetBackup sends this output
to the server as part of the backup and the resulting backup can abort with an
error message pertaining to block sizes. Also, ensure that all commands in the
scripts are appropriate to the client platform. For example, the -s parameter is
invalid for the UNIX mail command on some UNIX platforms and its use can
cause data to be written to stdout or stderr, resulting an error.Message was edited by:
RK