bpend_notify_busy

[nbuno]

Guys i want to configure this script so that i can get an email of the files those were busy while backup was running..
i have copied bpend_notify_busy script to /usr/openv/netbackup/bin but i don't know what else to do now ? Do i need to change some parameters to get this script working ?..which all ?

i have made changes to host properties-->client--> busy file setting as well  (operator e-mail address/working directory/process busy file-->send e-mail and file path in file action tab)..what now ??

[Nate_D1]

Is the script erroring, or is it not returning the data you want?  If its erroring on the bpend_notify_busy (like it cant find it) maybe your script needs to start in that path or you need to add it to the environment variables? More info will help troubleshoot!

[nbuno]

Its not about errors actually..its about how do i configure it..do i need to keep that script and expect it to work or do i have to tweak it ? thanks anyways :)

[CRZ]

First, you need to be sure you've renamed it to bpend_notify (or a policy/schedule specific version of bpend_notify) in addition to moving it into /usr/openv/netbackup/bin - I can't tell whether you've done that or not from your post, but it's an important step.

Second, you need to ensure you've properly configured the Busy File Settings properties for your client.  The documentation may help here:

Busy File Settings properties on UNIX/Linux
 http://symantec.com/docs/HOWTO66674

Activating the Busy File Settings in host properties on UNIX/Linux
 http://symantec.com/docs/HOWTO66675

This is taken from the "Admin Guide, Vol. 1" - I believe this is the 7.5 version, but don't know if it's any different from the other 7.x manuals.  It would have helped if you had told us what version you were running.  Here's all three:

Symantec NetBackup 7.0 Administrator's Guide for UNIX and Linux, Volume I
 http://symantec.com/docs/TECH127081

Symantec NetBackup 7.1 Administrator's Guide for UNIX and Linux, Volume I
 http://symantec.com/docs/DOC3650

Symantec NetBackup 7.5 Administrator's Guide for UNIX and Linux, Volume I
 http://symantec.com/docs/DOC5157

Hope this helps!

[nbuno]

Thanks Chris

No I have not remaned it to bpend_notify..i just copied it to /usr/openv/netbackup/bin and it still has the name as bpend_notify_busy..and what if i want to keep it working for all policies and schedules and not for some specific policy say bpend_notify.X(policy name).. ? do i still need to change its name to that coz i think we can make changes at host properties-client-client properties-busy file settings and then NBU should pick by itself for which client i want to have this thing applied..right ?

btw,i m using 7.1

[Will_Restore · Accepted solution]

To activate Busy File Settings

1. Copy the bpend_notify_busy script:

   /usr/openv/netbackup/bin/goodies/bpend_notify_busy

   to the path:

   /usr/openv/netbackup/bin/bpend_notify

2. Set the file access permissions to allow group and others to run bpend_notify. (chmod 555)

3. Configure a policy with a user backup schedule for the busy file backups.

   This policy services the backup requests that the repeat option in the actions file generates. The policy name is significant. By default, NetBackup alphabetically searches (uppercase characters first) for the first available policy with a user backup schedule and an open backup window. For example, a policy name of AAA_busy_files is selected ahead of B_policy

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

[CRZ]

You gotta read the documentation.  I'm not sure how else to put it.  The fact that you're still asking me if the script needs to be renamed... I mean, not only does the documentation say it, but I said it as the very first thing up there in my last reply!

Go back, read the documentation, follow the instructions, configure a client or two using the Busy File Settings, and see if the results are what you're expecting.

If it's still not working, keep in mind that YOU CAN'T CONTINUE TO CALL IT bpend_notify_busy AND EXPECT IT WILL WORK BECAUSE IT WILL NOT.

(Sorry for shouting.  I'm just trying to help!)