Thanks for the suggestions.
I checked again and the service labeled as "Removable Storage" was not
running/started. I changed it to DISABLED to make sure.
Yes, these are FC attached Magstar 3590E1A drives, so they have to be
accessed/shared via SAN and TSM Library Sharing.
Not sure I understand about not needing the TSM device drivers started.
Who does the device number assignment (i.e. mt188.8.131.52) since that is how I
point the path of the "library manager TSM server" to the "library client
TSM server" ?
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/02/2004 02:17 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
ADSM-L AT VM.MARIST DOT EDU
Re: Windows TSM server and sharing 3494 ATL across SAN
My Windows is Win2K and my 3494 is Lan not SAN; BUT:
You are using the IBM MAGSTAR drivers for the 3590 drives, yes?
So you don't need the TSM device driver started.
on Win2K, you have to go in to Windows services and DISABLE the Windows
service when you are using the 3590's,
or Windows will try to grab them at boot time.
Don't know if that applies to Win3K or not, but take a look...
From: Zoltan Forray/AC/VCU [mailto:zforray AT VCU DOT EDU]
Sent: Friday, April 02, 2004 1:32 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Windows TSM server and sharing 3494 ATL across SAN
Is this a workable configuration ?
So far, all of my attempts at making this work, say it isn't.
The major problem is that as soon as I enable the 3494/3590E1A drives on
the Windows box (2003), I start getting "drive inaccessibilty" failures on
the AIX TSM server. The SAN connection is via Qlogic 2342 cards.
I realize this is the Microsoft way (you will be
assimilated..............resistance is futile......;--) ).
Before I trash this attempt and install RedHat AS 2.1 (or will AS 3 work
for TSM on Linux), does anyone such a configuration that actually works
and "plays nice"!