Reclaim Process calling for vol from different Stg Pool

joxers64

ADSM.ORG Member
Joined
Feb 3, 2010
Messages
12
Reaction score
0
Points
0
PREDATAR Control23

Hi There,

I have taken over a TSM infra and discovered this reoccurring message in the actlog during reclaim:

ANR1044I Removable volume VOLUME is required for space reclamation. (SESSION: 119011, PROCESS: 5115)
ANR8308I 240: LTO volume VOLUME is required for use in library LIBRARY; CHECKIN LIBVOLUME required within 5 minutes. (SESSION: 119011, PROCESS: 5115)
ANR8313E Volume VOLUME is not present in library
LIBRARY. (SESSION: 119011, PROCESS: 5115)
ANR1402W Mount request denied for volume VOLUME - volume unavailable. (SESSION: 119011, PROCESS: 5115)
ANR1410W Access mode for volume VOLUME now set to "unavailable". (SESSION: 119011, PROCESS: 5115)

Above is generated when running reclamation for STG_POOL_1_OFFSITE

however,

when querying the vol it returns the following:
Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
VOLUME STG_POOL_2_ONSITE LTODEVCLA- 443.4 G 63.6 Full
SS

TSM Version 5.5
OS Windows 2k3
Library with 5 LTO3

Library is full, so have had to remove onsite tapes for onsite storage using move media command

It would appear that the database has 2 entries for this volume, one each for

STG_POOL_1_OFFSITE
&
STG_POOL_2_ONSITE


I suspect that this STG_POOL_1_OFFSITE volume was checked in as private and then became scratch, and was defined to the stg STG_POOL_2_ONSITE, which has created this issue.

Actions:
queried the actlog for the volume
it doesn't go back far enough to discover what happened to this volume
run a restore vol VOLUME copystoragepool=STG_POOL_1_OFFSITE preview=yes
this produces a list of volumes to be recalled from offsite for restore
run a restore vol VOLUME copystoragepool=STG_POOL_2_OFFSITE preview=yes
this produces a different list of volumes to be recalled from offsite for restore

So am in a good place where I can restore the volume to both stgpools, however my query is will it work as below:

update vol VOLUME access=destroyed
checkin the (vols listed above) status=pri
update vol (vols listed above) access=reado
then run the above restore commands again without preview
update (vols listed above) to offsite
checkout the vols listed above
del vol VOLUME discard=yes
 
PREDATAR Control23

Why will you set VOLUME to destroy? Is this an onsite volume?

Have tried to set to readwrite or readonly and see if reclamation will work?

If the volume VOLUME cannot be read, have you tried to run an audit?
 
Top