SOLARIS: Error nbjm(pid=2624) NBU status: 800

[jared009]

I have one windows2003 server runs as master server, one windows2000 runs as a test client server and two solaris 5.7 running db application as clients.

After replacing a tape drive in the HP MSL6030, I tried to make tests through windows2000 client and solaris client.

The windows client test is successfully done, but the solaris client test gave this detailed report after running:

2007-12-19 9:19:45 PM - requesting resource db1-data-bbc-hcart2-robot-tld-0
2007-12-19 9:19:45 PM - requesting resource dg-file-server.NBU_CLIENT.MAXJOBS.db1-data-bbc
2007-12-19 9:19:45 PM - requesting resource dg-file-server.NBU_POLICY.MAXJOBS.NEAP_level0
2007-12-19 9:19:45 PM - Error nbjm(pid=2624) NBU status: 800, EMM status: All compatible drive paths are down, but media is available
resource request failed(800)

I think it was an error that db1 cannot found the robot/tape drive.

Can you give me any suggestion?

Message Edited by jared009 on 12-19-2007 06:51 PM

[Stumpr2]

DOCUMENTATION: How to update NetBackup for a replaced tape drive without deleting and re-adding the drive

http://support.veritas.com/docs/271366

Details:

Manual: Veritas NetBackup (tm) 6.0 Commands for UNIX, Pages: 420-423
Modification Type: Supplement

Modification:
When a tape drive is replaced, the Veritas NetBackup (tm) configuration will need to be updated to reflect the changed drive. Once the drive is replaced, run the following command to report the discrepancy:

/usr/openv/volmgr/bin/tpautoconf -report_disc

This produces information similar to the following:

======================= New Device (Tape) ============
Inquiry = "QUANTUM DLT7000         245F"
Serial Number = PXA51S3232
Drive Path = /dev/rmt/21cbn
Found as TLD(0), Drive = 1
===================== Missing Device (Drive) =========
Drive Name = QUANTUMDLT70001
Drive Path = /dev/rmt/11cbn
Inquiry = "QUANTUM DLT7000         245F"
Serial Number = PXA51S3587
TLD(0) definition, Drive = 1
Hosts configured for this device:
Host = HOSTA
Host = HOSTB

This reports the discrepancy between the device database and the new device found. Take note of the new Drive Path for the device as this will be needed for the tpautoconf command.  To resolve this, run:

# cd /usr/openv/volmgr/bin
#./tpautoconf -replace_drive QUANTUMDLT70001 -path /dev/rmt/21cbn

Found a matching device in global DB, QUANTUMDLT70001 on host HOSTA
update of local DB on host HOSTA completed
globalDB update for host HOSTA completed

Found a matching device in global DB, QUANTUMDLT70001 on host HOSTB
update of local DB on host HOSTB completed
globalDB update for host HOSTB completed

This will update the global and local database to reflect the new device being replaced.

[jared009]

Thank you very much.

but I got these returns after the command:

root@db1-data-bbc # ./tpautoconf -report_disc

======================= Missing Device (Drive) =======================

 Drive Name = HP.ULTRIUM2-SCSI.001

 Drive Path = /dev/rmt/0cbn

 Inquiry = "HP      Ultrium 2-SCSI  F59W"

 Serial Number = HUL5H03346

 TLD(0) definition Drive = 2

 Hosts configured for this device:

  Host = db1-data-bbc

=========== Missing Device or no local control path (Robot) ===========

 Defined as robotic TLD(0)

 Inquiry = "HP      MSL6000 Series  0512"

 Serial Number = USX538005G

 Robot Control Host = dg-file-server

 Drive = 2, Drive Name = HP.ULTRIUM2-SCSI.001, Serial Number = HUL5H03346

 Hosts configured for this device:

  Host = db1-data-bbc

I also ran this:

root@db1-data-bbc # cfgadm -al

Ap_Id                                   Type         Receptacle   Occupant    Condition

c0                                       scsi-bus     connected    configured   unknown

c0::dsk/c0t0d0                     CD-ROM    connected    configured   unknown

c1                                        fc-private   connected    configured   unknown

c1::500000e010972bb1           disk         connected    configured   unknown

c1::500000e010972be1           disk         connected    configured   unknown

c1::500000e010976101           disk         connected    configured   unknown

c1::500000e010976121           disk         connected    configured   unknown

c1::500000e010976271           disk         connected    configured   unknown

c1::500000e010981f81            disk         connected    configured   unknown

c1::50800200001efbc9            ESI          connected    configured   unknown

c2                                        fc-fabric     connected    configured   unknown

c2::100000e0022322a3     med-changer  connected    configured   unusable

c2::256000c0ffc7d453             disk         connected    configured   unknown

c2::5006016030212afc            disk         connected    configured   unknown

c2::5006016830212afc            disk         connected    configured   unknown

c3                                         fc-fabric    connected    configured   unknown

c3::5006016130212afc            disk         connected    configured   unknown

c3::5006016930212afc            disk         connected    configured   unknown

pcisch0:hpc1_slot0             unknown      empty        unconfigured unknown

pcisch0:hpc1_slot1             unknown      empty        unconfigured unknown

pcisch0:hpc1_slot2             unknown      empty        unconfigured unknown

pcisch0:hpc1_slot3             unknown      empty        unconfigured unknown

pcisch2:hpc2_slot4             unknown      empty        unconfigured unknown

pcisch2:hpc2_slot5               fibre/hp     connected    configured   ok

pcisch2:hpc2_slot6               fibre/hp     connected    configured   ok

pcisch3:hpc0_slot7             unknown      empty        unconfigured unknown

pcisch3:hpc0_slot8              pci-pci/hp   connected    configured   ok

usb0/1                               unknown      empty        unconfigured ok

usb0/2                               unknown      empty        unconfigured ok

usb0/3                               unknown      empty        unconfigured ok

usb0/4                               unknown      empty        unconfigured ok

It seems that these deviced has not been correctly configured in the system, right?

I wonder how to configure that as I know only a little about Solaris 5.9

Message Edited by jared009 on 12-20-2007 11:42 PM

Message Edited by jared009 on 12-20-2007 11:43 PM