Kyle,

If you do not have your copypool set to collocate, the copypool tapes will
be used more efficiently.

Just update your copy  stgpool  accordingly.


Gabriel C. Wiley
ADSM/TSM Administrator
AIX Support
Phone 1-614-308-6709
Pager  1-877-489-2867
Fax      1-614-308-6637
Cell       1-740-972-6441


Kyle Sparger <ksparger AT DIALTONEINTERNET DOT NET>@VM.MARIST.EDU> on 10/25/2001
07:36:34 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Tape Copy pools and Colocation


Hello,

I'm starting to implement tape copy pools.  My primary pool has colocation
enabled, in order to speed up restores.  My primary storage pool currently
is using 27 tapes at varying degrees of usage.  When I did a test BACKUP
STGPOOL, the output indicated that it wanted to use another 27 tapes, even
though that would end up leaving unused space on each tape.

I expect that the copy pool will not be used a whole lot;  I intend to
move these tapes out of the library after each backup, and as such, prefer
density and tape efficiency to speed of recovery from these tapes.

I was wondering if there is a way to have it use the copy pool such that
it uses the fewest tapes possible, filling up each tape fully before
pulling another one from scratch.

Or, does it do this already, and is the test run just being
ultra-conservative?

Thanks,

Kyle Sparger - System Administrator
ksparger AT dialtone DOT com - http://www.dialtone.com
Voice - (954) 581-0097 x 122
Why do programmers get Halloween and Christmas mixed up? OCT(31)=DEC(25)