Yes, we have two libraries............
We only defined one library to the DR server for the switch, library it
could access.
The problem was the incorrect I.D. from the ibmatl.conf was selected
for the lmcp
definition to AIX.
It because available because it was acccessible from the lan.
The drives became available because they were accessible from the
switch.
So the command was going to one library where the volume was not, the
drives
were not, and TSM did not know anything of it contents.
It was confusing to see the volumes in the other library still showing
with a 'q libvol',
but the ones I was trying to access not.
Now I have an explanation.
>>> [EMAIL PROTECTED] 03/14/2005 3:21:42 PM >>>
On Mar 14, 2005, at 3:02 PM, Lawrence Clark wrote:
> In a library containing a Library Manager, such as the 3494, TSM
does
> not need to know (and does not know) where tapes reside within the
> library.
>
>>>> Is this true? It does seem that when the contents of a Q LIBVOL
> came up emnpty was the point that TSM could not mount a volume. I
mean,
> if you have 2 libraries defined, how does TSM know which library to
> send
> the command to for a specific volume?
Yes, it's true.
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.
TSM knows which of your library definitions to send its commands to by
virtue of your TSM definitions: you defined a Library instance, and
then the physical Path to the library, where the Path specified a
unique /dev/lmcp_, which goes through the lmcpd and the
/etc/ibmatl.conf to reach the library. It is vital in initial phases
of
library use, such as your DR test, that you employ the mtlib command
to
verify these basics. A missing or faulty atl conf file, or lmcpd
functionality issue, will keep the arrangement from working. This
would
be reflected in your AIX Error Log. It is also the case that the 3494
needs its authorization list updated to allow access by each host
system in which TSM runs. And in some cases, the 3494 may be on a
non-routed subnet, which means that the TSM system must also have an
ethernet card on that same subnet. (Another path is via RS-232 rather
than TCP/IP, but few people bother with that any more.)
I'd recommend running tape inventory lists via the mtlib command to
verify that the inventory can be seen from the DR system, and that the
Category Codes reported match your TSM library definitions. If all
looks good, try mounting a volume on a tape drive via the mtlib
command
and see if that works. In AIX, be sure that the tape drives are in an
Available rather than Defined state.
References:
"IBM TotalStorage Tape Device Drivers: Installation and User's
Guide",
(GC35-0154) (a renaming of the earlier manual "IBM SCSI Tape
Drive,
Medium
Changer, and Library Device Drivers: Installation and User's
Guide", of the
same publication number)
"IBM TotalStorage Tape Device Drivers: Programming Reference"
(GC35-0346)
(a renaming of the earlier manual "IBM SCSI Tape Drive, Medium
Changer, and
Library Device Drivers: Programming Reference" (WB2107))
Available at ftp://ftp.storsys.ibm.com/devdrvr/Doc/
(refer to the .message or README file in that
directory)
or ftp://ftp.software.ibm.com/storage/devdrvr/Doc/ as
files:
IBM_TotalStorage_tape_IUG.ps or
IBM_TotalStorage_tape_IUG.pdf
IBM_TotalStorage_tape_PROGREF.ps or
IBM_TotalStorage_tape_PROGREF.pdf
Richard Sims
