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