Richard, this was a copy storage pool that it was running on. But I cannot
find anywhere in the manual that states copy storage pools perform
differently when it comes to setting the threshold hi and discontinuing
reclamation.
Remata, I see where it reports on what volumes it will work on when the
reclamation starts.

What I'm trying to do is make this as simple a scheduled process as
possible. But reclamation ran well into my backup cycle and used drives
that I was expecting to have available to backup to.




"Richard Sims" <rbs AT BU DOT EDU>@VM.MARIST.EDU> on 08/07/2001 09:33:21 AM

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: How reclamation doesn't work


>...Then at 14:30 I set the reclamation threshold back to 100 so
reclamation
>should stop right (upd stg nttapeco rec=100) Wrong.
>Reclamation continues to run until 02:30 the next am. ...

Jim - What kind of storage pool was involved?  The behavior you saw
      would be consistent with that for an offsite storage pool, as
per the Admin Ref manual topic "Choosing a Reclamation Threshold",
"Lowering the Migration Threshold".

   Richard Sims, BU