You may want to consider defining a separate storage pool heirarchy for
each of your 16 concurrent sessions (or split between 8 or ?).  That way
each disk pool would migrate to a different tape pool and thus a different
tape.  Up to 16 restore sessions would then be possible in parallel if you
have enough tape drives.  For the copy pool, its your choice on using a
single copy pool or use 16 different copy pools (or any number in between).
This would allow up to 16 restore sessions to proceed in parallel at the
Disaster recovery site.

Robert R. Price
ADSM/TSM Administrator
Computer Sciences Corporation
Phone: 412-374-3247
Fax: 412-374-6371
rprice28 AT csc DOT com


----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------





                      "MC Matt Cooper
                      (2838)"                  To:      ADSM-L AT VM.MARIST DOT 
EDU
                      <Matt.Cooper             cc:
                      @AMGREETINGS.COM         Subject: Need your thoughts on 
best RESTORE approach
                      >
                      Sent by: "ADSM:
                      Dist Stor
                      Manager" <ADSM-L


                      06/21/04 02:47
                      PM
                      Please respond
                      to "ADSM: Dist
                      Stor Manager"






Hello all,
     We backup an ORACLE ERP that is about 350GB.  We back it up by
running a script that uses  16 concurrent sessions, each one backing up
a series of File Systems, all sesions going to disk pool.  It is
compressed by the client.    This method works well.  We backup the data
in less than 2 hrs and it looks like 130GB of compressed data.   I know
the data will be single threaded through 1 tape drive to tape during
migration, because it is all coming from the same server.  The offsite
copy is then made running tapepool to copypool, (yes I know it would be
better to make the offsite from disk first but I do not have enough disk
for enough time to do that).    I know that our 9840 tapes will be
getting about 20GB each so there should be 5 or 6 tapes (at least)
containing this servers backup.
    What would be the optimal way of doing the RESTORE of this data?
Ideally I ask TSM to just use 6 drives and all is well or know where the
break points are on the tapes.  Has anyone worked (and tested) this out
yet?  Our current attempts take about 18-24 hours
Thanks in advance
Matt