This is a new 5.2.2.x install. The drivers are labeled IBM. I am pretty sure I got them from IBM Magstar support, directly.!
"Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/02/2004 02:50 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: Windows TSM server and sharing 3494 ATL across SAN Windows does the device number assignment. According to the doc for the Windows TSM server, you use the TSM SCSI drivers for 3590 drives with a TSM 5.1 server, BUT you must use the Magstar tape drivers INSTEAD of the TSM SCSI driver with a TSM 5.2 server. It's documented in the Getting Started guide for Windows TSM 5.2. If you're still on 5.1, forget I mentioned it... -----Original Message----- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Windows TSM server and sharing 3494 ATL across SAN 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. mt3.0.0.1) since that is how I point the path of the "library manager TSM server" to the "library client TSM server" ? "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/02/2004 02:17 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: Windows TSM server and sharing 3494 ATL across SAN Zoltan, 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. AND, on Win2K, you have to go in to Windows services and DISABLE the Windows RSM 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... Wanda -----Original Message----- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:32 PM To: [EMAIL PROTECTED] 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"!
