> Hi,
> is the removable storage service on the w2k3 box disabled?If not do so.
Not sure. I turned the box off and haven't had any more problems. I will
restart and disable it.
> Have you configured the library to use the tsmscsi.sys driver? Not the
Microsoft
> driver.
As I mentioned, it dosn't see the library itself, just the tape drives.
How do I do this ?
> Have you installed the IBM tape driver for w2k3 using the "for Tivoli
Storage Manager" option.
Yes, I did.
>
> Best Regards
>
> Markus Veit
>
>
>
>
>
>
>
> An: ADSM-L AT VM.MARIST DOT
> EDU
> Kopie:
> Thema: Multi-TSM
> configuration questions (and now issues)
>
> owner-adsm-l AT VM.MARIST DOT EDU
> Received : 10.03.2004
> 19:55
> Bitte antworten an "ADSM:
> Dist Stor Manager"
>
>
>
>
>
> Not sure if this message got lost and now that I am having some issues,
I
> am reposting..
>
> Yesterday, I installed TSM on the 2K3 system (described below). Now, my
> original TSM AIX system is starting to experience problems like this:
>
>
> 3/9/2004 2:50:27 PM ANR8779E Unable to open drive /dev/rmt0, error
> number=16.
> 3/9/2004 2:51:06 PM ANR8381E 3590 volume 070040 could not be mounted in
> drive ATL-DRIVE1 (/dev/rmt0).
> 3/9/2004 2:51:06 PM ANR1402W Mount request denied for volume 070040 -
> volume unavailable.
> 3/9/2004 2:51:06 PM ANR1410W Access mode for volume 070040 now set to
> "unavailable".
> 3/9/2004 2:51:06 PM ANR9999D afrtrv.c(688): ThreadId Unexpected result
> code (157) from ssRtrv.
>
> My AIX guy says the "=16" means the drive is "in use/busy". However,
> neither of the other two system I am building, are configured to use the
> 3494ATL, yet. The drives are defined but that is it !
>
> So, what gives ? Is the proposed configuration workable or problematic
?
> Is TSM designed to handle such a configuration ?
>
> BTW, the original AIX server is at 5.2.1.3 while the new AIX and 2K3
> system are at 5.2.2.0.
>
>
*********************************************************************************************************************
>
>
> I am in the middle of a large, multi-TSM, shared-library, different OS,
> different platform configuration process. Here is the layout:
>
> Current Configuration
> -------------------------------
> 1-3494 ATL which consists of 8-3590B, ESCON attached drives (uses
> exclusively by our z/OS system) and 4-3590E1A FC attached drives via SAN
> 1-TSM z/OS server (A)
> 1-TSM AIX server using the E1A drives in the ATL (B)
>
> Future Configuration (adding to existing configuration - nothing will be
> removed)
> ------------------------------
> 1-3583-L72 Library with 2-3580 LTO2 drives accessed via SAN
> 1-TSM AIX server (C)
> 1-TSM WINDOWS 2003 server (D)
>
> For a total of 4-TSM servers accessing/sharing 2-Tape Libraries with
each
> TSM server needing to access both libraries, simultaneously !
>
> The additional servers is mostly due to HIPPA/Firewall requirements
(don't
> go there............)
>
> Here is what I need to setup/configure.
>
> Both the new AIX (C) and 2K3 (D) TSM servers will need to access/share
the
> E1A drives and the LTO2 drives. Whether the existing TSM AIX (B) server
> needs to access the LTO2, has not been discussed but probably likely.
>
> I have been digging through the books and understand that ALL (with the
> exception of the TSM zOS server) need to be crossed-defined to each
other,
> so that they can communicate with each other as to who has what drive,
> etc. However, never having done such a configuration, I am somewhat
> unsure of all the pieces-parts and configuration needed to set eveything
> up properly.
>
> I know about the different library PRIVATE/SCRATCH category codes for
the
> 3494 ATL and defining the libraries as SHARED. I also understand about
> having to checkin/checkout the tapes that each TSM server will be using.
> Also, I have configured all of the LAN definitions to the 3494 ATL, for
> all of the sharing/managing systems.
>
> Never having done a WINDOWS based TSM, so I am a little confused on the
> hardware definition aspect. For instance, while I was able to install
the
> drivers for the tape drives the box sees, via SAN/FC, I can't seem to
find
> a definition for the 3494 ATL library itself while the 3583 LTO library
is
> coming up as an "unknown library". The TSM devices are there (i.e. the
> 3585 is lb0.1.0.2) but what do I use when defining the path ? When I
> tried using the lb0.... it did not like it ?
>
> Any help/suggestions/recommendations/thoughts on this configuration
> "challenge" will be greatly appreciated !!!
>
> Sorry about being so long-winded.......
|
