Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+What\s+tells\s+Q\s+DRM\?\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] What tells Q DRM? (score: 1)
Author: Paul Dudley <pdudley AT ANL.COM DOT AU>
Date: Tue, 18 Mar 2008 14:31:13 +1100
What process is it that tells Q DRM which tapes are in "vault retrieve" status? Is it Expiration or Space Reclamation? The reason I am asking is that we have not had any tapes in "vault retrieve" sta
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-03/msg00245.html (11,151 bytes)

2. Re: [ADSM-L] What tells Q DRM? (score: 1)
Author: Wanda Prather <wprather AT JASI DOT COM>
Date: Tue, 18 Mar 2008 00:37:48 -0400
Usually it takes both. Expiration is what causes the %utilization and %reclaimable values for your tapes to be updated. If you aren't running reclamation, those values won't change (unless you delete
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-03/msg00246.html (12,850 bytes)

3. Re: [ADSM-L] What tells Q DRM? (score: 1)
Author: Steven Harris <sjharris AT AU1.IBM DOT COM>
Date: Tue, 18 Mar 2008 15:46:42 +1100
And as to what actually makes a tape change state? Once an hour TSM runs an internal check. Tapes change from pending to scratch/empty when their pending period is past and the check is run. You have
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-03/msg00247.html (13,944 bytes)


This search system is powered by Namazu