As you have already learned the hard way, library sharing would not work
if you have not defined paths to *all* drives for sharing.
Quote from TSM for AIX, Managed System for SAN Storage Agent User's Guide
(GC32-0771-00; just the same wording I quoted for v4.2 in June last year):
"Define paths to all drives. Problems can occur if you do not define paths
from the server to each drive in a library."
In the TSM for AIX Administrator's Guide the requirement is not mandatory:
"Define the drives in the library ...
Note: We recommend that you define all the drives in the shared library to
the library client and library manager servers."
Actually TSM Storage Agent is cut down server code. And I would bet that
the docs have to be updated showing mandatory requirement for the server
as well. Thinking the server code has some kind of library-sharing
extensions (to take into account only drives with defined paths) over the
storage agent seems less possible.
Zlatko Krastev
IT Consultant
"Anthonijsz, Marcel M SITI-ITDGE13" <Marcel.Anthonijsz AT SHELL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
19.05.2003 13:05
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: 3584 Library sharing problems.
To all,
I've a bit of a challenge.
We're running TSM 5.1.6.3 on two AIX systems sharing a 3584 Tape library
system.
One AIX server acts as library manager with the library definitions and
paths and drives.
The AIX server acting as client only has the 'shared library' definition
and one tape path relating it to the Library manager.
So far no problems all seems to work fine.
Now I want to add another TSM server to this running on AIX, same level
also 4.3.3, but running TSM 4.2.1.15.
So this is what I did:
On library manager - defined the TSM server running 4.2.1.15
- defined tape path(s) to new server, only those
'known' to the new client due to the zoning of the switch to which the
client is connected
On library client - defined shared library
- defined shared drives
- defined new device class for the new to use
library
Here comes the real problem; when I start a process on the client which
requests a tape, the client starts a session with the Library manager and
the manager starts the mount of a scratch tapes and then informs the
client via another session about which volume is mounted and on what
drive.
Then until now I've got a 100 % score on mismatching, for the manager
loads the tapes on drives NOT known by the client, what is exactly what
the client shows in the actlog and the process gets cancelled.
What I don't understand is WHY does the manager NOT load the scratch tape
on a drive related to the tape paths defined for this client, it just
seems to pick any available drive and informs the client.
What's the use then of defining the paths if they're not taken into
account during the mount?
Marcel Anthonijsz
Central Data Storage Manager (a.k.a. storman)
Shell Information Technology International B.V.
PO Box 1027, 2260 BA Leidschendam, The Netherlands
Tel: +31-70 303 4984
Mob: +31-6 24 23 6522
|
