OK, so I down'd the problematic drive and it still bought the farm.  If
I setup a seperate machine, import the db catalogue from the db tape,
and try a restore, is there the possibility the data I'm looking for
would still be available?  The reason I ask is that the media is read
for a long time, several hours, before it barfs.  If the data I need is
before the bad spot, or not even on that tape at all (6 tapes for this
image) then I should be golden.  It's just the import to create the
image is bombing correct?

Thanks.

~JK

Larry Kingery wrote:
> 
> Jeff Kennedy writes:
> > Is there a way to tell an import to only use a specific drive?
> 
> Put the tape in the drive before you start the import?
> 
> > Currently I am having problems with a particular media id in an image
> > that keeps failing with a read error.  But it always fails in the same
> > drive.  I want to try this import in a different drive and see what
> > happens. I am using a bidfile for phase 2 import.
> 
> Down the drive having problems?
> 
> >
> > Also, I tried to dd the tape to a filesystem (fs=400+gb's) but it said
> > not enough space.  Any ideas why?
> 
> It has to do with block size.  Try setting the block size parameter
> for dd to the same as NBU (32k, 64k, or whatever you may have changed
> it to).  This is of course assuming you've located to the right file
> mark as per appx C of NBU SAG.
> 
> >
> > Thanks.
> > --
> > =====================
> > Jeff Kennedy
> > Unix Administrator
> > AMCC
> > jlkennedy AT amcc DOT com
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> --
> Larry Kingery
>          "Cut down a tree with a herring? It can't be done!"

-- 
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com