This is an issue for me, especially if you need to use the NEW_STREAM
directive yet would like your backups to be scheduled by netbackup to
take advantage of the checkpoint restart features for netbackup 5.0.

For example, say you have 6 "NEW_STREAMS".  Using bpstart_notify to kick
off an action such as shutting down a database will be invoked once for
each "NEW_STREAM".  

Does anyone have a solution for handling multiple stream when used in
conjunction with bpstart/bpend??

Charles Harris
Jet Propulsion Laboratory
IBS Systems Storage & Unix
Phone: (818)393-5297
Fax:     (818)393-4541
Cell:     (626)676-1425
Email:  Charles.L.Harris AT jpl.nasa DOT gov


-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Peter
DrakeUnderkoffler
Sent: Monday, November 17, 2003 11:13 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Multiple stream bpstart_notify and bpend_notify...


Hello all,

Not sure if I reinvented the wheel, but a wrote a complete bpstart/bpend
notify script set to handle multiple streams. Unfortunately, the client
wanted me to write it in a shell instead of perl.  I have two
questions...


1.  Is there already a good solution for "Standard" policies for this
that I just haven't found yet?

2.  If no to the questions above, any reason anyone knows of that the
start/end scripts couldn't be written in perl?  I know the start gets
passed 4 arguments and the end script gets 5, the same first 4 followed
by the status of bpbkar.  Additionally, there are environment variables
set such as..

STREAM_NUMBER
STREAM_COUNT
UNIXBACKUPTIME
BACKUPTIME
STREAM_PID
BACKUPID

Anything else anyone know of?   I think I can be much more efficient
with logging and error handling within perl.


Thanks
Peter DrakeUnderkoffler


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu