We were able to get the library defined. The README distinctly lacks the
define drive command for Win2K. Does this mean it is isn't necessary? That
somehow RSM provides drives to the RSM defined library?
Is this freaking magic or what?
Thanks,
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: Petr Pxerost [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 10, 2001 1:36 AM
To: [EMAIL PROTECTED]
Subject: Re: IBM 3583 and Ultrium Drives, Windows 2000
Yes , I did .
You have to use device driver from
ftp://service.boulder.ibm.com/storage/devdrvr/Win2000/ - this driver enable
integration of 3583 into MS Removable Storage manager . Everythink works
fine if all drives and library are on the
same SCSI bus . MS has problems with multiple SCSI busses - that
configuration needs registry editing and
description in W2K resourse kit is wrong. Throught RSM you can test various
functions of library ( open IO port ,
eject , inject , audit ) - I recommed to test everything ( now I am running
driver 5.1.0.8 and everything looks fine ).
You have to be familiar with RSM - TSM use this as external library manager
!
In TSM you define 3583 as RSM automatic library according TSM server readme
( minimum version is 4.1.1 ).
Before you can use tapes in TSM you have to move all tapes to free media
folder in RSM - there is NO
checkin process !
I still can not understand some operations in RSM environment ( move media ,
restore DB ... ) and
I really appreciate information from anybody who did some work in this area.
I wonder if this is common Tivoli direction in W2K - ADSMSCSI driver ( my
opinion ) is much better ,
I understand that with RSM I can share 3583 between various applications but
I don't know many
customers with such requirement. Combination TSM and RSM creates
complications even with such
simple task as removing DB backup copy from library - you have to identify
tape in TSM then do eject
in RSM - it's not easy to automate.
Kelly , If you will have some more specific question mail me directly.
Regards
Petr
----- Pyvodnm zprava -----
Od: Kelly J. Lipp <[EMAIL PROTECTED]>
Komu: <[EMAIL PROTECTED]>
Odeslano: 10. ledna 2001 3:29
Pxedmlt: IBM 3583 and Ultrium Drives, Windows 2000
> This is a reprise of a thread started in December.
>
> Flame on:
>
> HAS ANYONE MADE THIS WORK WITH TSM 4.1???????
>
> Flame off.
>
> The documentation is not clear: Does ADSMSCSI support this baby or do we
> need to use the device drivers shipped with the library? The library
> documentation suggests that if you are going to use TSM you should not use
> the drivers shipped with the library. If, on the other hand, you simply
> start the TSM device driver, one can't see the drives.
>
> Could anyone that has made this work please document here what you did?
>
> Thanks,
>
> BTW, if we figure it out we'll post what we learned.
>
>
> Kelly J. Lipp
> Storage Solutions Specialists, Inc.
> PO Box 51313
> Colorado Springs CO 80949-1313
> (719) 531-5926
> Fax: (240) 539-7175
> Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
> www.storsol.com
> www.storserver.com
