This is great news, because I have been frustrated by the slow restores.
I do have one question, though.  We installed our DLT drives while still on
a release of MPE that didn't explicitly support DLT, so we "faked it out"
with another device ID as suggested here.  We were told to use
"COMP3480" because we use labeled tapes for our backup, and the DDS
device ID wouldn't work with labeled tapes.  Is anyone aware of such a
problem?  Are any of you who use HPC1521B using labeled tapes?

>>> Lee Gunter <[log in to unmask]> 06/18/98 08:36pm >>>
Gilles is correct ... the HPC1521B device ID works very well for our DLT's
on all our systems.  We were advised by our backup software vendor
not to
use the 'DLT4000' device ID, yet, for just this reason.

Lee Gunter          [log in to unmask]




From: [log in to unmask] on 06/17/98 05:19 PM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: Request for comment on backup proced




At 05:45 PM 98/06/17 -0600, you wrote:
...snip
>Despite the speed hype of DLTs, it takes us over 3 hours to restore files
>(even small ones) from a strip set. They deffinetly hold more data but
>access speed to specific data is sllooww.
....
Actually, the problem with lengthy restore times is due to the fact that
the default DLT driver does not support the "fast search" feature we've
learned to appreciate with our 4mm dat drives.
The workaround to this problem is to simply configure the DLT using
device
id HPC1521B - instead of DLT4000 - until HP releases the appropriate
fast-search-enabled driver for DLT4000, which, AFAIK, is still in beta,
although I would gladly stand corrected.
The workaround works very well and has lasted quite a long time at the
two
sites I know that are using it.
---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]
---------------------------------------------------------------------------