OK,
This begs some additional discussion.  This presumes that there is a one to
one relationship between the device class and the storage class in the TSM
environment.  But, there is probably not a single installation like that.  I
believe in this case the installation only wanted to move some tapes to the
new library, not all.  In the all scenario, changing the device class works
fine.

The issue that I see is that a storage pool in the future will need to span
more than one library simply because of the number of needed devices and
exploiting the flexibility of SANs.  I hope TSM Development is working on
this.

In our case we have two 3494s, one with 16 drives and one with 22 drives.
It is really a pain to have to worry about which library a tape will be
inserted into when it returns from the offsite storage.  It also limits us
when a SAN client is limited to one library for a storage pool of scratches
because the storage pool cannot span, but I can see how difficult it could
get to support cross library functionality.

So, I guess the only way to move from one library to another is by doing a
client move from one storage pool to another.

-----Original Message-----
From: Kelly Lipp [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 25, 2001 3:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Changing Library box


Not quite.  You need to update at the device class that pointed to old
library and have it point to the new library:

update devclass devclassname library=newlib

Then TSM will look for the old device class volumes in the new library.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Seay, Paul
Sent: Sunday, November 25, 2001 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Changing Library box


I have been wondering the answer to this question myself and did some
research.  According to the administrator's guide what you did is the proper
way to checkout and checkin a volume to a library.  But, it does not say you
can move the volume to a new library (device class/storage pool).

This is what I am speculating.  You cannot change the device class of a in a
storage pool without deleting and redefining it.  Once a tape has a private
status I am betting you cannot do what you are trying to do.  However, if
the tape has no data on it and you change its status from private to scratch
I am betting you can check it out and back in to a different library.

Yes, this sucks.  Remember TSM manages objects between storage pools.  So,
you can move all the data off a volume easily with the move command.  Then
you should be able to change the status of the volume to scratch and move
it.  I do not know if you will have to run expiration to be able to change
the volume's status.

I have not tried this but bet that this is the situation.

I think there is a requirement here for us to be able to associate a super
device class to a storage pool that contains many libraries and to be able
to change the location of a volume so long as it is in the super device
class.

Maybe Andy has an idea.

-----Original Message-----
From: Michel David [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 25, 2001 6:31 AM
To: [EMAIL PROTECTED]
Subject: Changing Library box


Hi all TSM'rs

I want to change my library from 20-tape lib to a
bigger. I connected both of them together to reansfer
the tapes.

for a tape name 000104
I made
Checkout libv oldlib 000104
I eject the tape
checkin libv newlib 000104

q libv seems to be OK.
q libv:
newlib 000104 data

When I try to make an audit vol or Retrieve (with API)
 He look's for the Tape IN THE OLD LIBRARY !!!

What can I do to convince him ??
Please HELP !!!

Michel
MARNET.

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

Reply via email to