DOCUMENTATION: The scripts bpstart_notify and bpend_notify will run during catalog backups on a master server.

Article:TECH38439  |  Created: 2005-01-19  |  Updated: 2005-01-21  |  Article URL http://www.symantec.com/docs/TECH38439
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: The scripts bpstart_notify and bpend_notify will run during catalog backups on a master server.

Solution



Manual:  NetBackup (tm) System Administrator's Guide for UNIX, Volume II, for version 5.0 and 5.1

Page: Section 6, NetBackup Notify Scripts

Modification Type:  Addition

Modification:

The scripts bpstart_notify and bpend_notify will run during execution of a catalog backup if they reside on the master server in the in the /<install_path>/netbackup/bin directory. This behavior is by design.


Workarounds:

To prevent this behavior, there are two available workarounds:

1.  Add a .policyname or a .policyname.schedule extension to the bpstart_notify and/or bpend_notify scripts

For .policyname, specify the name of a policy; NetBackup would then execute the script only for that policy. Example:  For a policy named "test," the file name would be bpstart_notify.test or bpend_notify.test.

For .policyname.schedule, specify the name of a policy and a schedule name; this would further limit the execution of the script to a specific schedule within the specified policy name given. Example: For a policy named "test," with a schedule named "weekly," the file name would be bpstart_notify.test. weekly or bpend_notify.test.weekly.

For more information on these scripts, please refer to the NetBackup System Administrators Guide for UNIX, Volume II.

2.  Modify the script to filter the arguments of ''unknown''

For example, add the following to the bpstart_notify or bpend_notify script:

if [ ''$4'' = ''unknown'' ] then
 exit 0
fi





Legacy ID



276447


Article URL http://www.symantec.com/docs/TECH38439


Terms of use for this information are found in Legal Notices