OK, everybody's at the latest AIX and TSM 5.5.2.  The shared library manager, 
NT, now handles CAPEKLIB1 for N1-N6 and has no clients of its own.  The 
thinking behind this was that NT could be restarted in an instant with nothing 
more than the default DB and Log.  So NAS clients have to talk to a different 
library, right?  And Mr. SAN, two desks down, says all physical connections 
should be LANFree (and Liverpool just scored against Real Madrid on tape, so 
I've got distractions).  My reading of manuals is that the NAS can't use NT as 
it is currently used.  That's why I created the second logical library on the 
TS3500.

Fred Johanson
TSM Administrator
University of Chicago

773-702-8464


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Wanda Prather
Sent: Wednesday, February 25, 2009 11:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] How to define Library2

Please give your TSM server version & platform when posting, you'll get
better results.  I can only assume that "NT" here is a Windows box and you
are running at least TSm 5.4.  You also don't say whether you intend to
backup the NAS via Lan-Free or TCP/IP; they are quite different

I don't understand why you are creating a new logical library in the TS3500
for this instead of using the existing one; but since you are doing it this
way, SOME TSM server has to own library CAPEKLIB2.  It's not clear from your
post whether you want NT to own it also, or N6 (which presumably is also a
client of CAPEKLIB1, which is allowed).

But I'm assuming you want it to belong to N6, non-shared:

a) use the library web interface to create a "control point" on a drive in
logical library CAPEKLIB2.
b) zone the library & drives so they are jvisible on the SAN to N6
c) In Windows Device Manager, right click and select "scan for new
hardware".
d) In the TSM Management Console Device Driver window, you should now have a
new lbx.x.x.y and new drives mtx.x.x.y.

Then you can do your DEFINE LIBRARY.

W

On Wed, Feb 25, 2009 at 11:47 PM, Fred Johanson <Fred AT uchicago DOT edu> 
wrote:

> For years we've lived happily in the situation of TSM instance (and
> machine) NT whose only function is to serve as library manager for our 6
> production (N1-N6) and test (N7) TSM.  NT controls a TS3500 named CAPEK
> which has a logical library (1-01) known to N1-N6 as CAPEKLIB1.  So far,
> everything works finem no questions.
>
> Now we're setting up TSM for NAS.  Our first NAS client will live on N6.
>  We have defined on CAPEK a new virtual library (1-02) with the appropriate
> drives and label range.  We think of this as CAPEKLIB2, an entity distinct
> from the active shared Library Manager defined on N1-N6 as CAPEKLIB1.
>
> So now I sit at the command line of N6 and worry.  If I enter the command
> "def libr CAPEKLIB2 shared=no etc., etc." I don't see how that associates
> with the virtual library 1-02 on the TS3500.  I'm obviously missing
> something as plain as the nose on my face, but what is it?
>
> Fred Johanson
> TSM Administrator
> University of Chicago
>
> 773-702-8464
>