It sounds like your COPY pool has colocation enabled. Just turn that off for the copy pool, leave it on for the primary pool.
-----Original Message----- From: Kyle Sparger [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 10:37 AM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] - http://www.dialtone.com Voice - (954) 581-0097 x 122 Why do programmers get Halloween and Christmas mixed up? OCT(31)=DEC(25)
