Roger,

I am not on a stable ground on this issue but always thought that
reclamation threshold is compared to result set by expiration in VOLUMES
table. So calculation is performed only once (during expiration - now I am
careful which word am using :-). And later comparision is not expensive -
you cannot have millions of volumes so the table is not big and is easy to
traverse.
And I think both migration and reclamation are fired same way and retried
in a minute.
Just an opinion.

Zlatko Krastev
IT Consultant




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:        Re: Reclamation is not happening - HELP!

This happened to me once. After pulling what remains of my hair out, I
tried simply restarting the server. That fixed it.

Also remember that the server checks the list of volumes to see if they
can be reclaimed only about once an hour. (It's costly to calculate.) So
any changes you make to the threshold level might not cause reclamation
to start until as much as an hour later.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu


On Sat, 18 May 2002, Zlatko Krastev wrote:

>AFAIK during backup files are not 'marked' at all. They are just stored
>and during reclamation each file is compared to rules defined in its
>mgmtclass copygroup. That why reclamation takes so long.
>If you backup a file and according to *current* rules a version should
>expire, later update copygroup to retain more versions (or for longer
>period) and just afterward run expiration - the file should not be
>expired. If it is marked during backup/archive it would expire which
would
>be against ADSM/TSM ideology and should be treated as bug.
>
>Jack, sometimes it helps to change reclamation/migration threshold to 100
>and minute or two later to lower it. I've digged deeper to analyse why.
>
>Zlatko Krastev
>IT Consultant
>
>
>
>
>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:        Re: Reclamation is not happening - HELP!
>
>Jack,
>  As TSM ages backup and archive data, the files only get 'marked' for
>deletion. You must run an EXPIRE INVENTORY command to actually flip the
>switch from 'marked' for deletion to deleted. Then your storage pool
>reclamation should work.
>
>  That is, unless I am missing something too!!!  8-)
>
>John G. Talafous              IS Technical Principal
>The Timken Company            Global Software Support
>P.O. Box 6927                 Data Management
>1835 Dueber Ave. S.W.         Phone: (330)-471-3390
>Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
>talafous AT timken DOT com           http://www.timken.com
>
>
>-----Original Message-----
>From: Coats, Jack [mailto:Jack.Coats AT BANKSTERLING DOT COM]
>Sent: Friday, May 17, 2002 1:50 PM
>To: ADSM-L AT vm.marist DOT edu
>Subject: Reclamation is not happening - HELP!
>
>
>My tape use is going up, but nothing is being reclaimed from my copy
pool.
>I must have done something wrong, but where do I go to look for whatever
>is
>wrong first?
>What am I missing?
>
>I can find nothing in the activity log, and even when I do a
>
>        update stg copypool rec=5
>
>and it should recover a lot, nothing happens.  Sometimes the process
>starts
>up, but will sit for hours and nothing gets reclaimed.
>
>Running TSM 4.1.5 on NT, with 3583 library and LTO drives.
>It has been working, but stopped earlier this week.
>
>... TIA ... Jack
>