[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

660.0. "file not found error - Tape drive started with wrong name" by OTOOA::kap901.kao.dec.com::trimble () Tue May 06 1997 11:33

I had a problem the other day with Networker 4.2 on an 
Alpha NT 3.51 server.  I have two tape drives on the 
system, a DAT and a DLT.  The DAT is in a StorageWorks
module, so I often take it out to share with other 
systems in our data center.  Problem was, when I took
it out the other day, I rebooted the system while the
drive was out.  When I went to put the drive in, the
device driver wouldn't load for it.  Also, Networker
had renamed my DLT drive to be \\.\Tape0 instead of 
the \\.\Tape1 it used to be.  

Now I have everthing working again, but if I insert
the DAT drive again, and reboot, it will be seen as
\\.\Tape0 again and screw up my config again.  

Does anyone know how to change the DAT drive driver 
to load after the DLT driver to make sure that the
DLT drive remains as \\.\Tape0???


Regards,

Jason Trimble
[email protected]

T.RTitleUserPersonal
Name
DateLines
660.1please send complaints to Bill...montlake.zso.dec.com::lenoxreply to [email protected] or decwet::lenoxTue May 06 1997 14:2018
NetWorker didn't rename your DLT drive to \\.\Tape0,
NT did (when you rebooted NT with only the one drive on
it, check out the Registry for yourself), and since you already
had \\.\Tape0 defined to NetWorker, it didn't know what
you had done behind its back.  This behavior is actually noted
in the admin guide, which I noticed after this odd behavior
happened to me.  (Since on unix it doesn't matter, I wasn't
used to NT's way of working).

This stuff usually depends on the scsi ids used, so if
your DAT drive was id 1 before and the DLT drive
at id 2, then try putting your DAT drive at 3....  this is
only an example.  This isn't a NetWorker issue, this is
an NT issue.  It may work differently between NT 3.51
and NT 4.0, so be warned.  If you don't have any ids to
spare, you may have to fuss and put it back to the original
setup.
660.2DECWET::RANDALLTue May 06 1997 14:215
You could try making certain that the SCSI ID of the DAT drive
is lower then the SCSI ID of the DLT drive.  I'm not positive this
will work.  Amy would know better.

-- Rich Randall