Highlighted
2 Bronze

39078:nsrjb: RAP error: No jukeboxes are currently usable

My company ust recently moved locations here locally and I am trying to get the backups up and running again but I am running into the "39078:nsrjb: RAP error: No jukeboxes are currently usable" error. I read somewhere online of the jbverify commands and what it does, so hopefully this will help. The main issue I am running into is when the Networker goes to switch tapes in the IScalar Jukebox it fails and sits and retry and will constantly retry to unload the tape (There are no tapes loaded into the tape drives because I manually logged into the Juke and ejected them). Below is the jbverify results and any help would be greatly appreciated:

H:\>Nsrjb -II

39078:nsrjb: RAP error: No jukeboxes are currently usable.

H:\>jbverify

14866:jbverify:

Jbverify is running on host alcbackup01, Windows Server 2003 5.2

14912:jbverify:

Processing stand-alone devices...

14913:jbverify:

Processing q:\SQL\_AF_readonly

14915:jbverify:

Finished processing q:\SQL\_AF_readonly

14913:jbverify:

Processing g:\File_Servers\_AF_readonly

14915:jbverify:

Finished processing g:\File_Servers\_AF_readonly

14913:jbverify:

Processing q:\exch\_AF_readonly

14915:jbverify:

Finished processing q:\exch\_AF_readonly

14913:jbverify:

Processing q:\SQL

14915:jbverify:

Finished processing q:\SQL

14913:jbverify:

Processing q:\exch

14915:jbverify:

Finished processing q:\exch

14913:jbverify:

Processing p:\NDMP\_AF_readonly

14915:jbverify:

Finished processing p:\NDMP\_AF_readonly

14913:jbverify:

Processing p:\OracletoDisktwo

14915:jbverify:

Finished processing p:\OracletoDisktwo

14913:jbverify:

Processing g:\File_Servers

14915:jbverify:

Finished processing g:\File_Servers

14913:jbverify:

Processing p:\OracletoDisktwo\_AF_readonly

14915:jbverify:

Finished processing p:\OracletoDisktwo\_AF_readonly

14913:jbverify:

Processing p:\NDMP

14915:jbverify:

Finished processing p:\NDMP

14913:jbverify:

Processing g:\OracletoDisk\_AF_readonly

14915:jbverify:

Finished processing g:\OracletoDisk\_AF_readonly

14913:jbverify:

Processing g:\OracletoDisk

14915:jbverify:

Finished processing g:\OracletoDisk

14917:jbverify:

Finished processing stand-alone devices.

14918:jbverify:

Processing jukebox devices...

14920:jbverify:

Processing jukebox ALCJUKE:

16024:jbverify: Unable to open SJI device scsidev@3.2.1. Check device, connections and drivers.

39078:jbverify: SYSTEM error: No such file or directory

39077:jbverify: error, Cannot initialize jukebox! Driver may not be loaded!

14926:jbverify:

Failed while processing jukebox ALCJUKE on alcbackup01

14929:jbverify:

Finished processing jukebox devices.

**********************************************************************

                 Summary report of jbverify

                 ======= ====== == ========

Hostname   Device Handle    Blocksize  Jukebox  Drv No. Status

--------   -------------    ---------  -------  ------- ------

alcbackup01 q:\SQL\_AF_readonly 32768   N/A      N/A     Pass

alcbackup01 g:\File_Servers\_AF_readonly 32768 N/A N/A   Pass

alcbackup01 q:\exch\_AF_readonly 32768  N/A      N/A     Pass

alcbackup01 q:\SQL           32768      N/A      N/A     Pass

alcbackup01 q:\exch          32768      N/A      N/A     Pass

alcbackup01 p:\NDMP\_AF_readonly 32768  N/A      N/A     Pass

alcbackup01 p:\OracletoDisktwo 32768    N/A      N/A     Pass

alcbackup01 g:\File_Servers  32768      N/A      N/A     Pass

alcbackup01 p:\OracletoDisktwo\_AF_readonly 32768 N/A N/A Pass

alcbackup01 p:\NDMP          32768      N/A      N/A     Pass

alcbackup01 g:\OracletoDisk\_AF_readonly 32768 N/A N/A   Pass

alcbackup01 g:\OracletoDisk  32768      N/A      N/A     Pass

alcbackup01 Unknown          N/A        ALCJUKE  N/A     Fail

**********************************************************************

14938:jbverify:

Exiting jbverify with failures.

H:\>16024:jbverify: Unable to open SJI device scsidev@3.2.1. Check device, connections and drivers.

Reply
15 Replies
Highlighted
4 Germanium

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

It really looks like this is an 'ALF' jukebox ... an alien life form because so far you only know what you have done.

What does 'moved location' mean ? - Did you physically move the hardware or did you make a host transfer ?

Has the hardware changed at all ? - SCSI drivers, tape drivers etc. ?

The OS seems to be W2K3 but which NW version do you run ?

Is the Windows RSM service disabled ? - Has it re-enabled again ?

If all these basics have been verified, i think it is easier and faster to delete and reconfigure the jukebox. Or let it NW detect it itself.

Reply
Highlighted
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

Moved locations as in the physical building, the company moved locations locally and the servers are now stored offsite, The hard ware has not changed and the NW Version is 7.5.2 and yes the RSM is disabled.

Reply
Highlighted
4 Germanium

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

So what does "inquire" report? - does it see the robot and all drives as before?

Verify the SCSI addresses with your configuration.

Reply
Highlighted
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

I did the inquire command and this is what it said:

H:\>inquire

scsidev@0.0.0:HL-DT-STCDRW/DVD GCC4244B101|CD-ROM

scsidev@2.0.0:DELL    PERC 5/i        1.00|Disk

                                           WWNN=60013720662FFA000C6DFCE53773D421

scsidev@2.64.0:  RAID   DummyDevice    0001|Unknown Device Type

scsidev@3.0.0:IBM     ULTRIUM-TD3     93G0|Tape, \\.\Tape0

                                           S/N: 1210154483

                                           ATNN=IBM     ULTRIUM-TD3     1210154483

                                           WWNN=500308C099952000

                                           WWPN=500308C099952001

                                           PORT=00000001

scsidev@3.1.0:IBM     ULTRIUM-TD3     93G0|Tape, \\.\Tape1

                                           S/N: 1210366255

                                           ATNN=IBM     ULTRIUM-TD3     1210366255

                                           WWNN=500308C099952004

                                           WWPN=500308C099952005

                                           PORT=00000001

scsidev@4.0.0:DGC     RAID 5          0219|Disk

                                           S/N: FCNPR061300136

                                           WWNN=6006016083D21800702FFEBCECB4DE11

                                           PORT=00000002

scsidev@4.0.1:DGC     RAID 5          0219|Disk

                                           S/N: FCNPR061300136

                                           WWNN=6006016083D218001CED4DB0EAB4DE11

                                           PORT=00000002

scsidev@4.1.0:DGC     RAID 5          0220|Disk

                                           S/N: FCNPR062301112

                                           WWNN=6006016052841801AA1304E50C26DE11

                                           PORT=00000003

scsidev@4.2.0:DGC     RAID 5          0220|Disk

                                           S/N: FCNPR062301112

                                           WWNN=6006016052841801AA1304E50C26DE11

                                           PORT=00000002

H:\>

H:\>jbverify -j

14866:jbverify:

Jbverify is running on host alcbackup01, Windows Server 2003 5.2

14918:jbverify:

Processing jukebox devices...

14920:jbverify:

Processing jukebox ALCJUKE:

16024:jbverify: Unable to open SJI device scsidev@3.2.1. Check device, connections and drivers.

39078:jbverify: SYSTEM error: No such file or directory

39077:jbverify: error, Cannot initialize jukebox! Driver may not be loaded!

14926:jbverify:

Failed while processing jukebox ALCJUKE on alcbackup01

14929:jbverify:

Finished processing jukebox devices.

**********************************************************************

                 Summary report of jbverify

                 ======= ====== == ========

Hostname   Device Handle    Blocksize  Jukebox  Drv No. Status

--------   -------------    ---------  -------  ------- ------

alcbackup01 Unknown          N/A        ALCJUKE  N/A     Fail

**********************************************************************

14938:jbverify:

Exiting jbverify with failures.

Reply
Highlighted
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

Reading the inquire command it seems like it is just the connection, or am I missing something? It shows it reads the tape drives, just not the Juke.

Reply
Highlighted
4 Germanium

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

NW's 'INQUIRE' command uses the SCSI INQUIRE command.

In general, it 'pings' each possible SCSI and see whether the target answers. Then it uses additional information to get the details like type and vendor. That's the brief description.

As it turns out, you see the drives but not the robot (if it should be connected to the same computer). Here is ours:

scsidev@nn.0.0:GRAU    ITL-5000l       1.7 |Autochanger (Jukebox)

  ....

So check the connectivity issues and make sure that you see the hardware via the OS. Then rerun inquire before you proceed with anything else.

Reply
Highlighted
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

Thank you for the input Bingo and I think you got it right. It has to be the connection. I just hung up the phone talking to the Co-lo IT department that we are using to store or servers and they noticed one of the connections is not online, so this has to be the issue. I will update when I get back from going to the data center.

Reply
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

After much wire connection chasing, everything seems to be connected properly. Still having the same issue.

Reply
Highlighted
2 Bronze

Re: 39078:nsrjb: RAP error: No jukeboxes are currently usable

sizer2,

How do I do the following?


LD_LIBRARY_PATH variable needs to be set to include the non-default lib directory prior to NetWorker started up.

Reply