Just a word of warning. We had a very unsuccessful install of a 3583 with
TSM on a AIX box. The library turned out to be very unreliable to the point
where every component was replaced but still it did not function correctly.
In the end IBM held their hands up and admitted that there where issues
with this model. We are now running on a 3584 which is much better.
Good luck.
Neil Sharp
Dyadic Systems Limited
Tel : 01256-811125
E-mail : [EMAIL PROTECTED]
"Seay, Paul"
<seay_pd@NAPTHEO To: [EMAIL PROTECTED]
N.COM> cc:
Sent by: "ADSM: Subject: Re: IBM 3583 Library question.
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>
07/02/2002 06:11
Please respond
to "ADSM: Dist
Stor Manager"
Generally, you want to use *stcbn if it is available. The reason is the
drive will stay at the point between closes and reports the location block
on open. Remember these are smart drives like Magstar and can skip to a
block as requested. Typically, a backup product does that. However, I
will
defer to rest if they have a better answer.
-----Original Message-----
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 4:16 PM
To: [EMAIL PROTECTED]
Subject: IBM 3583 Library question.
We are hooking a new IBM 3583 tape library up to a Solaris
host to be a remote site TSM server. The Ultrium drives have various
/dev/?st... devices through which we can access them. The no-brainer was
to
use the driver that tells the drive to compress the data, but I'm not sure
between these 2 options:
/dev/rmt/*stc <- compression and "Rewind on Close"
/dev/rmt/*stcn <- compression but "No Rewind on Close"
I can't find anything in the TSM or library documents on which to
use. Does TSM get confused if a tape were to be mounted and it was not at
the beginning? Kind of seems like we would reduce tape and drive wear by
using the "no rewind" device drives, and writes might happen quicker it the
tape is not rewound...
Any suggestions would be helpful. (the listserv archive
site
is currently inaccessible.)
Thanks,
Ben
Micron Technology Inc.
