As I mentioned in the previous email, I determined the problem as being
the wrong ID was used for the lmcp def.
It was the ID of the other library.

Doing a 'q libvol' showed the volumes of the library with the ident,
but the ones from the library I was trying to
use were missing. This was a bit confusing until I determined where my
error was. It also suggest that table is
populated from information TSM derives from the library, since it
'flushed' that info from the library that was not
accessible.

q vol, and q con <vol> still showed info on the 'flushed' volumes
because that info is maintained solo by TSM and
not the library manager.

>>> [EMAIL PROTECTED] 03/14/2005 4:07:06 PM >>>
==> On Mon, 14 Mar 2005 15:21:42 -0500, Richard Sims <[EMAIL PROTECTED]>
said:


> In a library with a Library Manager, such as the 3494, TSM does not
mount
> the tape - the library does, per TSM simply asking the library to
mount
> volume 001234.


I'm going to have to dispute this.  I just tested on my 3494, and if
my
library manager doesn't see the volume in its' Q LIBVOL, it doesn't
acknowledge the existence of the tape.


I did the following:

1) Restored a file from a client (and therefore determined which tape
it was
   on)

2) CHECKOUT LIBVOLUME remove=no

3) Confirmed volume in scratch category

4) Attempted restore.  Library manager says "CHECKIN LIBVOLUME required
within
   60 minutes."

5) Canceled restore, checked in, checked out again.

6) used mtlib to assign the volume to the correct 'private' category.
(this
   would be analogous to the failed DR scenario)

7) Attempted restore.

8) Attempted restore.  Library manager says "CHECKIN LIBVOLUME required
within
   60 minutes."

... Cleaned up.



You may be confusing the "library manager"-ness of a 3494 with the
"library
manager"-ness of a TSM server.

My configuration has a 3494 attached to a library-manager TSM instance
(which
I call 'CTRL', for controller), and then other TSM instances request
mounts
from the CTRL instance.

When I Q libvol from CTRL, the volumes show up.  When I Q libvol from
a
library client, it's empty.



- Allen S. Rout

Reply via email to