you should fina all your netbackup keys in the following location

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion

you probably should be looking at the keys

INSTALLDIR, INI Directory, Log Directory

bp.conf on windows is under the folder CurrentVersion of above path as the folder Config

Here's what to do - at your own risk - I'm not responsible for any mistakes that you may make whilst using regedit.

1) CD to your goodies folder, e.g.

$ cd "C:\Program Files\VERITAS\NetBackup\bin\goodies"

2) listpaths > "%temp%\pre.txt"

3) regedit

...and browse to:

HKLM\SOFTWARE\Veritas\NetBackup\CurrentVersion\Paths

4) Create a new REG_SZ key named:

BPEND_NOTIFY

...and give it a value to the full path of your new bpend_notify script, e.g.:

C:\\NetBackup_Script\\bpend_notify.cmd

N.B. remember to use double back slashes... "\\" 

5) listpaths > "%temp%\post.txt"

6) fc "%temp%\pre.txt" "%temp%\post.txt"

To prove that the new path will be used.

And do similar for BPSTART_NOTIFY registry key if you wish.

HTH.

Further points:

Maintenance patch kits overwrite any modification you make to any of the notify scripts, i.e. any site specific mods are replaced with default scripts - BUT you shouldn't be affected because your scripts will actually reside in a different folder - BUT I can't confirm whether the patch installer will process/use your new registry keys and thus overwrite your scripts.  So take a backup (see below).

Also, I don't know whether a maintence pack will remove your site specific registry key tweaks for script paths.  So, always make a note of any mods that you make in your recovery/rebuild documentation.

Personally, I would create a new backup policy to backup your scripts folder - as you would with any other live production data/code.  Don't be tempted to backup the entire volume - as you may end up taking your catalog too - and don't (as I have seen in the past) then be tempted to then exclude the catalog directory in the client (i.e. master) folder/path/file exclusions list - as this will in turn mean that your hot catalog backup skips your catalog path - thus rendering your catalog backup useless.   So, just backup the scripts folder (plus any other non standard NetBackup folders that you might be using).  Keep it simple.

Thanks SDW303 for your advice.

I have tried it step by step and several reboots of the server and it doesn't work now I have moved the scripts into the new (and specified) directory.  I have even tried changing the bpstart_notify.cmd setting in the registry to bpstart_notify.bat.

Even though the listpaths script gave the correct details of the path it still didn't use it. 

Any further advice greatfully received :D

Did "listpaths" definitely show the new path and file name?

Did you use double backslashes "\\" in the path-name file specification?

Is the drive, all folders in the tree, and the script files all readable by "everyone"?  If the script contains code that writes to disk (e.g. a temporary file of some sort) does the NetBackup process (which usually runs as NT_System_Authority) has access rights?

Just tested it too.  Didn't work for me either.  That's pretty disappointing.  Apologies if I've led you up the garden path - so to speak.  Looks like you'll either have to modify the normal bpend_notify to call yours - or IMHO, just modify the one in the "/bin" folder.

Further points to note:

- The BPRES file must be honoured, NetBackup uses this to determine whether your client specific post backup commands work or not.  i.e. your script must write a final status value to the file named in parameter %%6.   With a zero being success.

- Absolutely no output must be written to stdout by your script, otherwise the controlling job treats this as data and gets confused and will probably fail - i.e. your scripts must run, work and fail (if needed) silently and gracefully.