Using the stream numbers for the bpend process will not work, since
you can't predict which streams will end first. Say you have 5
streams, and stream #2 takes the longest. How do you know which one
should restart the database?

Typically what is done is have the scripts keep a counter of some
sort, and when each stream ends it decreases the counter. You have to
be careful of race conditions on the counter file (if that's how you
implement it), and of automatic reruns in case of errors.

-Craig

----- Original Message -----
From: Cornely, David <david_cornely AT intuit DOT com>
Date: Mon, 12 Jul 2004 14:16:29 -0700
Subject: RE: [Veritas-bu] bpstart_notify, and bpend_notify
To: veritas-bu AT mailman.eng.auburn DOT edu






















This
is actually the way it's designed.  Bpstart and bpend know which
stream they are so you have to script them to perform the actions you desire
based on the actual stream #.  For example, if you want to stop the
database with the first stream using bpstart you could maybe put an if
statement in to test and determine what stream it actually is and then shutdown
the DB if it's stream 1.



 



For bpend the same rules apply, execute an
action based on the stream #.  There are built in variables (e.g., STREAM_NUMBER
is one of them) that carry this information.  Check this support doc for more
info:



http://seer.support.veritas.com/docs/242081.htm




 



-Dave





 



-----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 Scalone, 
Galen

Sent: Monday, July 12, 2004 13:03

To:
Veritas-bu AT mailman.eng.auburn DOT edu

Subject: [Veritas-bu]
bpstart_notify, and bpend_notify



 



List, 

Here
is the setup: NB 4.5 MP6 on NT. 

Client
is HPUX 11.11. 

Policy
name is hostname.database. ( helen.sblprod) 

Schedule
is sblprod.daily, or sblprod.weekly 

The
policy consists of 8 filesystems, all separate streams. 

The
notify scripts are bpstart_notify.helen.sblprod, and bpend_notify.helen.sblprod
(notice no schedule in the name) 

These
notify scripts get run for each filesystem, not for the policy, and I'm not
sure why. The notify scripts shut a database down, and start it back up, but it
does it 8 times.



The library is 6 LTO-2 drives, and the storage units
are single drive units, six of them. 

Any
help appreciated.