Neil,
The VTL does not connect to the real library. It does not mount
tapes itself. All tape mounting comes from the TSM library master. We
do not use the feature that allows a VTL to mount tapes and copy virtual
tape data to a real tape.
It is a good thought, Neil, but I don't see anything in our
configuration besides the TSM library master that can control the tape
library.
Best Regards,
John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email: [EMAIL PROTECTED]
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Strand, Neil B.
Sent: Friday, September 05, 2008 1:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM library problem caused by IBM3584 virtual I/O
John,
It almost sounds like something is moving the tapes without telling
TSM. Is your VTL attached to the library?
Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Friday, September 05, 2008 12:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM library problem caused by IBM3584 virtual I/O
Greetings,
We are running TSM 5.4.3.0 on AIX 5.3ML5. We have a library master
instance, and 9 other TSM instances that are library clients. They all
share an IBM3584 with 24 LTO4 tape drives, and an EMC EDL virtual
library emulating an IBM3584 with 128 LTO1 drives.
Recently our IBM CE told us we should be running with virtual I/O, a
feature of the IBM3584 library. The reason he recommended it is because
we frequently have more than 32 outgoing tapes every day, and sometimes
the Operators don't get around to taking the tapes out of the I/O doors,
and checkouts have to wait. With virtual I/O turned on, the checkouts
go ahead and run to completion, even though the tapes don't actually go
into the I/O doors. Then later when the I/O doors get empty, the tape
library moves the rest of the tapes into the I/O doors. That part seems
to be working as expected.
After we turned virtual I/O on, we started getting weird symptoms in
TSM, like tapes that we would check back in to the library, but later
TSM could not find them. So we decided that maybe virtual I/O changed
the element number map, and we should have redefined the library to TSM.
So we:
1) Deleted the drive paths, drives, library path, and library on the
library master instance, and all client instances.
2) From the Tape library Web interface, performed a complete library
inventory (just in case)
3) Defined the library, library path, drives, and drive paths on the
library master instance, and all client instances.
4) Checked back in the scratch tapes
5) Checked back in the private tapes
6) Did an Audit library on the library master and all library clients.
It was only a few days later that we started getting errors from TSM of
the form:
09/04/08 22:00:56 ANR8300E I/O error on library SUN2079
(OP=00006C03,
CC=314, KEY=05, ASC=3B, ASCQ=0E,
SENSE=70.00.05.00.00.00-
.00.0A.00.00.00.00.3B.0E.00.C0.00.04.,
Description=The
source slot or drive was empty in an attempt to
move a
volume). Refer to Appendix C in the 'Messages'
manual
for recommended action. (SESSION: 395703,
PROCESS: 487)
09/04/08 22:00:56 ANR8312E Volume 101781L4 could not be located in
library
SUN2079. (SESSION: 395703, PROCESS: 487)
09/04/08 22:00:56 ANR8358E Audit operation is required for library
SUN2079.
(SESSION: 395703, PROCESS: 487)
09/04/08 22:00:56 ANR8381E NAS volume 101781L4 could not be mounted
in drive
LTO4_F2_D09 (c576t0l0). (SESSION: 395703,
PROCESS: 487)
09/04/08 22:00:56 ANR1402W Mount request denied for volume 101781L4
- volume
unavailable. (SESSION: 395703, PROCESS: 487)
09/04/08 22:00:56 ANR1410W Access mode for volume 101781L4 now set
to
"unavailable". (SESSION: 395703, PROCESS: 487)
It is different tapes every time, so we now have over a dozen tapes that
are missing on account of this. Did we do something wrong with we
turned on virtual I/O for this library? I found this technote, that
sounds like it is supported. It also says we need to restart the TSM
server instance, which we have done now a couple of times since this
problem started.
With SAN Device Mapping implemented (since TSM520 for Windows and TSM530
for most other platforms), when hardware changes are done to the
library, the Tivoli Storage Manager server needs to be restarted. During
server initialization, Tivoli Storage Manager server will access the
library. If the library inventory has changed, it will be refreshed at
that time. If drives are added or deleted from the library or drive
element addresses are changed, this information will be refreshed at
server initialization also. If the library path has changed, then the
path needs to be updated with the new device name for the new library
path. The same holds true when dealing with a 3584 library with the ALMS
feature. This is discussed in the following document :
http://www-1.ibm.com/support/docview.wss?uid=swg21053638
That document will mention that "TSM supports the Advanced Library
Management System (ALMS) and Virtual I/O Slots (VIOS) features of IBM
3584. When changing the number of drive, storage, or import/export
elements for a logical library, the TSM server must be restarted."
Is there something else I needed to do in TSM? Some option in the
options file, or setting in the library?
Best Regards,
John D. Schneider
Lead Systems Administrator - Storage
Sisters of Mercy Health Systems
3637 South Geyer Road
St. Louis, MO 63127
Phone: 314-364-3150
Cell: 314-750-8721
Email: [EMAIL PROTECTED]
This e-mail contains information which (a) may be PROPRIETARY IN NATURE
OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only
for the use of the addressee(s) named above. If you are not the
addressee, or the person responsible for delivering this to the
addressee(s), you are notified that reading, copying or distributing
this e-mail is prohibited. If you have received this e-mail in error,
please contact the sender immediately.
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security
numbers, account numbers, or personal identification numbers. Delivery,
and or timely delivery of Internet mail is not guaranteed. Legg Mason
therefore recommends that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain
privileged or confidential information. Unless you are the intended
recipient, you may not use, copy or disclose to anyone any information
contained in this message. If you have received this message in error,
please notify the author by replying to this message and then kindly
delete the message. Thank you.
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.
