This is not a bug in TSM. Setting a volume unavailable makes the volume not
available to TSM and thus, TSM does not try to mount that volume for read
or write. But, TSM still has information regarding the valid data in the
volume. You can not remove a volume from a storage pool till the volume
keeps some valid data in it. You can remove the volume from the storage
pool by forcefully discarding the data from the volume. And then you have
to checkout the volume from the tape library before trying to re-lable the
volume.
Further, it is not necessary to re-lable the volume to reuse it. A volume
defined as private to a storage pool (after being used by that storage
pool) is reassigned to the library as scratch volume, once it gets empty
after expiration, reclaimation, or move data etc. And hence, it can be
reused.
Mahesh Prasad
DCM Data Systems Limited
New Delhi, India
Henrik Hansson
<Henrik_Hansson@A To: ADSM-L AT VM.MARIST DOT
EDU
LBINT.COM> cc:
Sent by: "ADSM: Subject: Overwrite volumes
Dist Stor
Manager"
<[email protected]
.EDU>
04/08/2002 02:38
PM
Please respond to
"ADSM: Dist Stor
Manager"
Hi,
I have problems relabel volumes in TSM. I have volumes defined in my
primary archive pool. These volumes I want to reuse so I updated the access
for thoose to unavailiable.
Then i tried to do a label libv with the parameter overwrite=yes. The
command fails with the message that the volume already is labeld and
belongs to a storage pool.
Is there a bug in TSM? Or is there a way to get passed this error.
I'm running TSM 4.2.1 on a AIX 4.3 system.
Thanx for all help
Med vänliga hälsningar / Best Regards
Albany Door Systems AB
Henrik Hansson
IS-Department
|
