Hoi Roark,

If you cannot affort to upgrade to 5.3.x, you can also use more tapepools.
So you can make a tapepool for very small nodes, with collocation off, so it
still uses less tapes and a tapepool for the big nodes with collocation on.
If neccesary, you can make more tapepools, but remember, if you want to use
a diskpool (and most sites do) you need a diskpool for each tapepool.
But best thing is to upgrade to 5.3.x and learn the command line commands
:-), so you can use collocation groups.

Collocation on copypools is most of the times nonsens... Even if you want it
in case of a big disaster, the costs are enormous and fast restores per
machine is not the biggest issue at that moment if you can use a library
with enoufh drives to restore multiple machines simmultanious.

You cannot change a "filling" tape to "full", but you can use "move data
{volname} stg={diskpool}" to move the data of the tape quickly to disk. If
you set the access of the tapes you want to clean to readonly first, the
data will be migrated to the filling tapes you don't want to clean.

Regards,
Maurice van 't Loo


----- Original Message -----
From: "Roark Ludwig" <Roark.Ludwig AT SUNHEALTH DOT ORG>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Friday, August 26, 2005 1:56 AM
Subject: Re: [ADSM-L] Question about Space Reclamation..


> I have been handed a TSM system in the past week that has been running for
> a year.  IT has collocation = yes for TAPEPOOL and COPYPOOLS.   this
system
> is running TSM 5.2.2.
>
> We have run out of tapes as the setting for collocation (yes) is trying to
> use a tape for each node (as I understand it, ,,please correct me if I am
> wrong)..
>
> We have decided that since we have about  80 volumes with less then 1%
> utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for
> the TAPEPOOL and COPYPOOLS.
>
> We are expecting to add another set of nodes and don't wish to consume
more
> of our volumes (with small percent utilization) as we add the nodes.
>
> Question ..
>
> Will this setting COLLOCATION=NO stop the addition of volumes?  (I expect
> the answer is YES,, please correct me if I am wrong.)
>
> Now to the second question.
>
> I see no easy way to have Space Reclamation condense the volumes included
> in the two pools as it will only process "FULL" volumes. (Again Please
jump
> in here).
>
> QUESTION:  is it acceptable to set the status from "FILLING" to "FULL" for
> the volumes with low percentage utilized to force Space Reclamation ?
>
> OR
>
> is there an easier way to accomplish the GOAL of reducing the number of
> volumes needed for the pools?    (given that we have set COLLOCATION=NO)
> or should we simply wait out the natural filling of the volumes and allow
> normal Space Reclamation as time proceeds?
>
>
> Has anyone done this in the past?
>
> How have others dealt with this??
>
>
> Thanks for any input.
>