1.  Backups jobs don't care about multiplexing, beyond their schedules
limiting it to not go above a certain number.  The storage unit should
handle that.  You can't use the NEW_STREAM parameter if passing bpbackup a
file list.  If you don't pass it a list and use the list from a class, you
can have multiple streams take effect, but the -w will only return you one
error code from all the streams, the highest numerically I believe.
        This is how I've handled this in the past when dealing with Autosys
backups and a file list that changed every night.  Have your initial script
take the file that lists everything to be backed up, and split it into so
many files that equal the number of streams you wish.  Then that script will
call however many backup scripts (equal to the number of file lists), each
of which calls bpbackup with a -w.  Each of these scripts also writes a
marker file into a directory.  When the bpbackpup finishes, it checks the
status, and if bad, it touches a FAILURE file and appends its file list to a
file-list-log file.  Then, whether bad or good, it removes its marker.
        The main script has kicked off however many other backup scripts at
the same time.  Now it sits there and every five minutes, checks to see if
they're any markers out there.  If so, it sleeps for five more.  When there
are no more markers, it checks to see if FAILURE is there, and if so, exits
with 13 (or whatever).  Otherwise, it exits 0.

2.  There's a STREAM_COUNT or STREAM_NUMBER parameter you can play with to
make sure you don't try and start it up or shut it down multiple times, or
early.  I believe this is covered in the AG, but you can probably also
search the archives for this.

Thanks,
Gregg Yurchak
VERITAS Consultant
Biloxi, MS
gregg AT veritas DOT com
Office: 1.228.822.9810
Cell:    1.228.324.6939




-----Original Message-----
From: Sixbury, Dan [mailto:sixbury AT celeritas DOT com]
Sent: Thursday, October 11, 2001 7:42 AM
To: EBU (E-mail)
Subject: [Veritas-bu] Using scripts for backups with multiplexing and/or
multistreaming .


1.  If you use a file list with bpbackup, is it smart enough to try to
initiate multiple jobs, so that you can achieve multiplexing and/or
multistreaming, or will it backup the files sequentially?  This assumes that
I have configured multiplexing for the class and storage unit and/or
multistreaming for the class being called from the script.

2.  If you are using mulitplexing/multistreaming and as an example you use a
start and stop script to shutdown a database, backup the files, then start
the database; How can you assure that the jobs complete before the end
script tries to run to start the database back up?  The start script would
shut down the database and backup the data files.  The end script would
start the database back up.  The script is used so that I can assure no
newly created data files are being missed.

I have used bpbackup in scripts before where I included the -w (wait) option
so that I could assure that the backup finished before moving onto the next
line in the script.  In this scenario I want to queue multiple jobs so that
I can multiplex and multistream.  What kind of check can be done from a
script so that I can assure that the backup jobs have completed before the
end script gets run?

Thanks,
Dan


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