8464ch09_Oper.fm Draft Document for Review February 7, 2020 3:15 pm The thresholds are listed in Table 9-17.  Table 9-17 Reclamation priority table Priority Condition Reclaim  schedule  honored Active data  threshold%  honored Number of  concurrent  reclaims Comments 1 Pool in Panic  scratch state No No At least one,  regardless of  idle drives. If  more idle  drives are  available,  more reclaims  are started,  up to the  maximum  limit. 2 Priority move Yes or No No At least one,  regardless of  idle drives. If  more idle  drives are  available,  more reclaims  are started,  up to the  maximum  limit. If a volume is within 10  days of a Secure Data  Erasure and still has  active data on it, it is  reclaimed at this priority.  An SDE priority move  accepts the inhibit reclaim  schedule. For a TS7700 MI-initiated  priority move, the option  to accept the inhibit  reclaim schedule is given  to the operator. 3 Pool in Low  scratch state Yes Yes At least one,  regardless of  idle drives. If  more idle  drives are  available,  more reclaims  are started,  up to the  maximum  limit. Volumes that are subject  to reclaim because of  Maximum Active Data,  Days Without Access,  Age of Last Data Written,  and Days Without Data  Inactivation use priority 3  or 4 reclamation. 4 Normal reclaim Yes Yes, select  from all  eligible  pools (Number of  idle drives  divided by 2)  minus 1 8 drv: 3 max 16 drv: 7 max Volumes that are subject  to reclaim because of  Maximum Active Data,  Days Without Access,  Age of Last Data Written,  and Days Without Data  Inactivation use priority 3  or 4 reclamation. Tips:  A physical drive is considered  idle  when no activity occurs for 10 minutes. The Inhibit Reclaim schedule is not accepted by the Secure Data Erase function for a  volume that includes no active data. 548  IBM TS7700 Release 5.0 Guide