For collocated pools, if there are available scratch tapes, a single node is
assigned to a tape. Only when you no longer have available scratch tapes
does TSM start "stacking" nodes on a tape. If you want to minimize tapes in
your copypool, I would suggest either not collocating or setting a low
enough maxscratch number to force TSM to start stacking multiple nodes on a
tape. For more informaiton, the Admin Guide has a section describing tape
selection criteria and precedence.
Alex
-----Original Message-----
From: Christoph Pilgram
[mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 5:33 AM
To: [EMAIL PROTECTED]
Subject: Reclamation of COPY-POOL-Volumes
Hy all,
we have two backup-server, where we write our data to a tape-library. For
all our tape-pools we have defined one copy-pool which links to the other
server where the data are written to a separate tape-pool (pool_extern). We
have defined collocation for all our pools. When I now run reclamation on
the copy_pool I see, that for all copy-pool-volume the server deletes, he
defines a new one where the rest of the data are transfered.
This seems to be logical (because the reclaimed volumes are not empty and
the rest of the data has to be handeled like this because collocation is on)
but what I wanted is to reduce the number of volumes in the copy-pool. How
can I manage this and what is the real right way to reclaim data in a
copy-pool (or do I have to set the 'Maximum Scratch Volumes
Allowed'-Parameter in the Copy-Pool-Definition to unlimited ?).
Thanks for help
Christoph
