Gary,

It's important to distinguish between onsite and offsite volume
reclamation.
The onsite ones are reclaimed as you describe. The current volume is
reclaimed, the current reclaim value is checked, and if reclaim has been
set back to 100 then there is no more reclamation.
The offsite storage pool volumes are handled differently. According to the
documentation (and this can be seen in practice) a single process is
responsible for reclaiming all of the offsite eligible volumes. This
process does not stop when the reclaim value is set to 100. It has a job to
do and will not be deterred! (unless you manually cancel it).

Does anyone know what will happen if a volume eligible for reclamation has
half a file, and the other half of the file is on a volume which is not
eligible for reclamation? What logic is applied under these circumstances?

I'll be checking the utilization of the remaining volumes as per Marian's
note.
Very curious!

Regards,

Eric Winters
IBM Global Services Australia
ZE06 (Zenith Centre - Tower A)
Level 6,
821 Pacific Highway
Chatswood NSW 2067
Sydney Australia
Ph:  +61-2-8448 4104
Fax: +61-2-8448 4006


Gary Ison <Gary.Ison AT MAIL.STATE.KY DOT US> on 17/03/2000 00:17:54

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Eric Winters/Australia/Contr/IBM)
Subject:  Re: reclamation of off-site volumes




Eric,

        I am not by any means sure of my understanding either but here
goes.

Reclamation is an internal, "hidden", process which is triggered
automatically on an hourly cycle.  Apparently, it is internally limited to
only a single driving process (the hidden part) that controls multiple
execution processes, which are what you see with the process query.  It
examines the volumes table entries for candidates which qualify under the
reclaim threshold.  Those qualifying volumes, regardless of storage pool,
are processed for reclamation.  When you adjust the threshold (at 10:00) to
lower the value to your recovery point on the storage pool(s), it also
triggers the "hidden" process.  The reclamation then proceeds until it
either processes all the qualifying entries or the threshold is reset.
When
you reset the threshold at 16:00, you effectively stop reclamation until
the
next reset at 10:00 the next day (or cycle).  The process then repeats
itself.  The threshold reset acts as a "cancel process" command to the
hidden reclamation driving process.

        Does this make sense?

        Gary L. Ison
        Governor's Office for Technology
        101 Cold Harbor Drive
        Frankfort, Ky.   40601
        Phone:  (502) 564-8724
            Fax:  (502) 564-6856
E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
DOT us>