Conference decwet::networker

what's NT 4.0 SSP?
              ^^^
For the record, I've used a TL810 series jukeboxes (TL812 and TL894)
with NT 4.0 SP1 without problems.

If he is trying to label, can I assume that the jukebox reset
(nsrjb -HEv) and inventory (nsrjb -IEv) worked ok?  Please
elaborate on how those commands worked.

When you say that the other backup tools worked, I don't believe
that you are referring to use of the robotic controller at all,
or are you?  Did those tools just use the tape drives or were
they able to use the jukebox devices and use the robotic controller?

Hi Ed,

  Please post a note describing the hardware involved.
Include length of cables, scsi adaptors, firmware rev
levels, etc.

thanks,

Amy

The most common problem with large multi-drive jukeboxes is that
NetWorker and the jukebox disagree about what is drive 1, etc.

In that case, the jukebox loads a tape into the top-right drive 
(for example), thinking that it is drive 1.  NetWorker then attempts
to label the tape in the drive on the bottom-left (which it thinks of
as drive 1), and things obviously don't work.

One experiment:

Delete the jukebox.

Manually load a tape into a drive.

Attempt to label the tape via NetWorker.

If it fails, try using the other devices via networker until you find the
one that has the tape in it.

Or:

Manually load tapes into all drives and then attempt to label them.

Or: 

Create the jukebox resource using jbconfig and request a tape to be
loaded, while standing physically next to the jukebox.  See if it moves
a tape around.  That will validate the NetWorker -> jukebox connection.

Kevin

    
      Please post a note describing the hardware involved.
    Include length of cables, scsi adaptors, firmware rev
    levels, etc.
        
    Alpha XL233 NT 4.3 running NT 4.0 SP2
    The TL810 is firmware 1.20
    the TZ88 is \\tape0 and firmware at DECCC33
                \\tape1
                \\tape2
                \\tape3
    connected to decpzsa Driver deckzpsx
    Cable length is a Digital cable 20 feet long.
    
    Thanks
    Ed

Another engineer here suggests you check if the device is
setup properly as described here: when one opens the door,
does the jukebox's robot scan everything (takes more than
a couple minutes to do this).  If not, one can change this
behavior at the control panel of the jukebox, I don't have
a manual handy for this, please have them refer to their
manual on what to do.  

If that isn't the problem, please have them try the following
when sitting in the \nsr\bin directory

DOS_WINDOW_COMMAND_LINE_PROMPT>set SJI_DEBUG = 5
DOS_WINDOW_COMMAND_LINE_PROMPT>sjiielm [email protected] (I think,
                                  .4 disappeared and it had the
				  proper reference).
DOS_WINDOW_COMMAND_LINE_PROMPT>sjirdtag [email protected]
DOS_WINDOW_COMMAND_LINE_PROMPT>sjirjc [email protected]    (May as well try them all)

It looks like all four drives are on one bus, they do know
that once they get this working, that will not give them
very good performance, no?

    Hi Amy,
    Entering the sji*** commands seem to reset the jukebox to a normal
    state. I had him do the lines listed in not .7, and reconfigure the
    jukebox using jbconfig, relabel(since he did not have anything on his
    tapes anyway) and all seems ok.
    
    Thanks
    Ed

Something else must have been wrong that your customer
is not saying, since those sji* commands don't reset anything.

Glad it is no longer a problem.