Have you seen this nifty tool for your PC's

Wake Up on Standby
http://www.dennisbabkin.com/php/download.php?what=...

Have you ever wondered if it's possible to wake up your system from a Stand-by mode or Hibernation programmatically? The answer is yes, it's possible. This simple utility will do it for you. Once activated it resides in the system and wakes it up at predefined time, runs a file and if necessary sends it into Stand-by mode, hibernates it or shuts it down. It can also be used to run scheduled operations every day, or on specific day(s).
Special features:

    * Can restore almost every Windows-based operating system from a Stand-by mode (and some from hibernation) that support ACPI (Advanced Configuration and Power Interface) (For support check computer's BIOS as well as Control Panel -> Power Options);
    * Can run a file or open a web page at a predetermined time after a wake-up event, during normal operation, or before performing power operation;
    * Can send system back to Stand-by mode (hibernate it, shut it down, or log off user) after a certain time interval;
    * Can detect if Stand-by mode (or hibernation) is supported by your system;
    * Can turn the monitor on and hold off screen-saver during the waiting time;
    * Can repair local area network and high-speed Internet connection upon waking up from a suspended state;
    * Can send system into Stand-by mode or hibernate it with more options than available through Operating System;
    * Can be incorporated into an in-car (entertainment) PC system to speed up booting time & save battery [more here];
    * Can be run from the Windows Command Line without user interaction;
    * Can be saved as a batch file for later use.

You could use the notify scripts. See the Admin Guides for more on that.

Think that's what Stuart is referring to when he mentions notify scripts.

bpstart_notify resides on the client but is triggered by backup request from the master.

I'm guessing these notify scripts are not part of version 3.6?  I just found out we are running an old version...

Think it should still work however. 

From the Backup Central board:
"Use the bpstart_notify and bpend_notify scripts found in /usr/openv/netbackup/bin/goodies. (It's bpstart_notify.bat and bpend_notify.bat on Windows.)

Copy them into the /usr/openv/netbackup/bin directory (or <install_dir>\Veritas\NetBackup\bin on Windows, and add the commands you want to run in the appropriate places in the script. "
 

It is embarassing, but that is our version.  I'm assuming the path referred to above is in the install CD?  I searched on the server and client and could not find these files...

There still is the possibility of user-directed backups instead of server-directed backups.

Thats what the user type schedule is for.

OK so whats the difference between the two: from research so far....

For Server-Directed restores you would at least need the following:

- all your clients MAC addresses (assuming these dont change or get altered via some method)
-- this would be used to broadcast on the network to wake them as they dont have an IP when asleep.
-- the wake up command would be initiated via the notify scripts as mentioned above.
-- the script would I assume wait some period for clients to startup. Be pingable etc.
-- backup started.
-- then post-backup a go to sleep command

Heres my thoughts on User directed restores:

- define a policy with all clients to be backed up
-- add a user schedule for off-peak times
-- use a tool like wake up on standby to wake up during that off-peak time
--- craft a command line using bpbackup for your client  to run after waking up
---- full and or inc based on date.
-- the wosb tool would shutdown on no activity afterwards.

Also the clients would need to be WOL compliant at BIOS and configured/verified in the NIC for WOL and or magic packets.

Conclusions
-------------
For the User-directed route a lot of work done configuring at the client side. Could be done via group policies if you have a large number of clients.?
For the server-directed, being able to broadcast to all your clients with the current MAC address.

It sounds a very plausible approach. Would be interested to hear how you got on.

A number of factors to consider, man power effort, power-cost-savings, hardware.

Just a thought what does the NetBackup Desktop Laptop Option give anything like this?

The leftfield alternative to this whole thing is looking at thin-clients in your infrastructure.

Some other interesting tools
http://lifehacker.com/348197/access-your-computer-...

Thanks for the great information Stuart.  I really do appreciate you guys trying to help me out!  We are definitely trying initiate backups from the server rather than the client with the intent of having one place to make updates versus hundreds of client tasks.  All systems can use WOL and magic packets can be sent from trusted servers.  I'm still having trouble tracking down where these notify scripts can be found.  I've downloaded the 3.6 admin guide, but find no mention of them.  I've cruised through the 3.6 install CD with the same results.  What am I missing? 

Be careful with your versions..there was no 3.6 release.. none that I remember

http://en.wikipedia.org/wiki/Netbackup#Major_releases

So what version of NetBackup are you running. And what OS platform is your master server. UNIX or WINDOWS and what version?

And backup notify scripts were around during the release 3 days as noted in this technote:
http://seer.entsupport.symantec.com/docs/232652.htm

So if nothing has changed, and I do believe thats the case...
The scripts should be here

/<install_path>/netbackup/bin/
backup_exit_notify
dbbackup_notify
parent_end_notify
restore_notify
session_start_notify
backup_notify      
diskfull_notify
parent_start_notify
session_notify 
userreq_notify

These also when called write to files in the same directory with the suffix filename of CALLED

The above list is taken from a 6.5 installation but have been there or abouts since the days of 3.4
Use a current admin guide to get details of what they do.

No, I'm positive it's 3.6 as I'm holding the Veritas NetBackup Pro 3.6 install CD in my hand.  I also found this page on Symantec's site with the release date of August 4, 2003: 
http://www.symantec.com/business/support/release_details.jsp?pid=15144. 

The admin guide can be found here:  ftp://exftpp.symantec.com/pub/support/products/NetBackup_Pro/261194.pdf 

The master server is actually a cluster of two servers running Win2K3 SP1.  I searched on both servers and these scripts just do not exist anywhere.  I'm wondering if these files were there as part of the original installation and possibly removed or were not installed by default?  I'm hoping to connect with our old teammate next week to see if he has any insight. 

If I can just get my hands on the scripts, at least I can perform some testing to see if it will work with our current version.  I will let you all know if I can get any more details from the previous owner of the app.  Thanks again for your help!

 I don't think Netbackup Pro is Netbackup. I think it was aimed at backing up the Desktop. Similar if not the same as the Desktop Laptop Option.  It operated separately from netbackup, though you could use the netbackup server as the repository. The bsstart_notify scripts will not exist unless you load the "netbackup client".

I thought we were talking about the same thing.  So NetBackup Pro is not the same as NetBackup?  If I look at the About Section of our PC clients, I see we are running v3.60.2.0 Build 298.  On the server, the backups of the clients are stored and managed there.  I hope to get with my former teammate today who hopefully can shed some light on things.