Re: DUPTAP command

[Neil Palmer <NeilP@xxxxxxxxxxx>]

A possibility.  Unfortunately it wasn't my system I ran the DUPTAP on so
it's not easy to check.

...Neil





Ilena Ayala <ilena@compuserve.com>
Sent by: midrange-l-admin@midrange.com
2002/01/14 22:44
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Subject:        Re: DUPTAP command


At 10:39 AM 1/14/02 -0500, Neil Palmer wrote:
>
>OK - more a story for comment than a specific question, but I could ask
>why does the DUPTAP command take so bl**dy long ?
<snippity snip>

>It makes absolutely no sense to me why DUPTAP takes so long to run - even
>longer than to run the actual save or restore jobs on much slower systems
>(although the restricting speed is no doubt the write speed to an
SLR5-4GB
>tape, not the CPW of the box).  Anyone else have any annoying
experiences,
>or knowledge, on this stupid command ?   ;-)

Resource contention was already covered, so I'll offer another
possibility.
 Is there any chance you had borderline media/dirty read/write heads that
could be causing retry attempts on the drive?  I think you can check the
number of errors on a tape in DST (tape stats or something... I'm not by a
terminal to pull it up and it's been awhile).

I'm especially wondering since one of the tapes was an 8mm and in my
experience they seem to be more prone to media issues than most other
media- one CE told me that a single pass with a cleaning cartridge often
wasn't enough, so when we cleaned the 8mm drives we cut TAA distribution
tapes on, the standard set we had was to do three passes (which was his
recommendation for doing after a media error.)

-Ilena Ayala