Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Drive status shows AVR should be TLD

Created: 21 Oct 2013 • Updated: 21 Oct 2014 | 11 comments
This issue has been solved. See solution.

We have two HP tape Libraries in netbakcup 6.5.4.  Both libraries have two drives.  All 4 were working fine.  6 months ago I used Tape library 2 to utilize Acronis backup for a temp project.

Now I reconnect Tape Library 2 fibers to netbackup and ran “Configure Storage devices”. 

Tape library 1 works fine.  One of the tape libraries 2 drives shows AVR and the other one show Missing Path.  I am trying to fix the AVR.  I cannot use quick Erase or Label.

What do I need to do to change AVR to TLD?

Thanks

Operating Systems:

Comments 11 CommentsJump to latest comment

mph999's picture

If the drives show as AVR it means that NBU either thinks the drive is configured as standalone, or, it has lost connectivity to the library.

1. From the robot control host, run robtest - can you connect to the library and do you get output from the command:
s d

2. If (1) does not work, you need to confirm the robot control host can correctly see the robot from the OS level. Until the OS can see the robot, NBU will never work.

3. Once (2) has been confirmed, if (1) still does not work rerun the config wizard.

If the drives are on a separate media server than the robot control host, when you run the wizard you have to make sure that on the first screen when you select the servers to scan you select both the media server with the drives + the robot control host at the same time. If you only select the media servers with the drives, then the drives will be configured as stand alone and will show as AVR.

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
baba20009's picture

Robtest returns the following:

Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = MISSING_PATH:MXA009Z37D
  TLD(1)     robotic path = {5,0,2,1}

Robot Selection
---------------
  1)  TLD 0
  2)  TLD 1
  3)  none/quit
Enter choice:

Selecting 1 return the following:

tldtest.exe -rn 0 -r MISSING_PATH:MXA009Z37D

Opening MISSING_PATH

Error retrieving credentials for NDMP robot host Missing_path.

 

mph999's picture

Well, that would appear to be at least part of the problem, you can't connect to the library.
The robot that works appears to be connected to a windows server, is the non-working robot meant to be connected to the same server ? If so, is it zoned correctly, can you see it in device manager ?

When the robot was removed for your testing, was it deleted from NBU, or just unplugged ? It could be worth deleting the robot from NBU config and re-ruinnng the wizard, having first made sure the robot can be seen correctly from the OS.

Not quite sure why we see NDMP mentioned - are there any NDMP devices in the environment ?
I have to go now as it's late and I need some sleep - I should have posted enough info for you to fix now.

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

As per Martin's excellent post - the OS has lost connectivity to TLD(0).  Start with Device Manager - scan for devices. What do you see under 'Medium Changer'?

The next step is to run 'scan' from cmd. (Command is in ...\veritas\volmgr\bin)
Please post output.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

baba20009's picture

Thanks both for replying:

Device Manager: Medium Changers show both libaries:

   Hewlett Packard MSL G3 Series Libray (x86 based)

   Hewlett Packard MSL G3 Series Library (x86 based) 

****

tpconfig -d

Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   HP.ULTRIUM4-SCSI.000 hcart  TLD(0)  DRIVE=1
      MISSING_PATH:{4,0,1,0}:HU10078YC0                                DOWN
1   HP.ULTRIUM4-SCSI.001 hcart  TLD(0)  DRIVE=2
      {4,0,3,0}                                                        UP
      {5,0,4,0}                                                        UP
2   HP.ULTRIUM4-SCSI.002 hcart  TLD(1)  DRIVE=1
      {4,0,1,0}                                                        UP
      {5,0,2,0}                                                        UP
3   HP.ULTRIUM4-SCSI.003 hcart  TLD(1)  DRIVE=2
      {4,0,2,0}                                                        UP
      {5,0,3,0}                                                        UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = MISSING_PATH:MXA009Z37D
  TLD(1)     SCSI coordinates = {5,0,2,1}

EMM Server = nbu1

***********

vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
nbu1                                       656000    ACTIVE
dalnbu01                                   656000    DEACTIVATED

                                PENDING REQUESTS

                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM4-SCSI.000     No      No                     No        hcart
    nbu1                       MISSING_PATH:{4,0,1,0}:HU10078YC0    DOWN

HP.ULTRIUM4-SCSI.001     No      No                     No        hcart
    nbu1                       {5,0,4,0}                            AVR
    nbu1                       {4,0,3,0}                            AVR

HP.ULTRIUM4-SCSI.002     No      No                     No        hcart
    nbu1                       {5,0,2,0}                            TLD
    nbu1                       {4,0,1,0}                            TLD

HP.ULTRIUM4-SCSI.003     No      No                     No        hcart
    nbu1                       {5,0,3,0}                            TLD
    nbu1                       {4,0,2,0}                            TLD

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

SCAN

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 4; Bus: 0; Target: 1; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1007904N"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 4; Bus: 0; Target: 1; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z3H9"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z3H9"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1007904N"
Drive 2 Serial Number      : "HU1926620D"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1926620D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape5"
Passthru Name: "Tape5"
Volume Header: ""
Port: 4; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU184849VH"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 5; Bus: 0; Target: 2; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1007904N"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer1"
Passthru Name: "Changer1"
Volume Header: ""
Port: 5; Bus: 0; Target: 2; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z3H9"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z3H9"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1007904N"
Drive 2 Serial Number      : "HU1926620D"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 5; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1926620D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 5; Bus: 0; Target: 4; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU184849VH"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
 

 

 

 

RamNagalla's picture

  TLD(0)     SCSI coordinates = MISSING_PATH:MXA009Z37D

Scan is also not seeing TLD 0 robot.. you need to check in the Zoaning level to see if everying is fine or not..

if everything looks fine in the zoaning level try to reboot the server once and see how it takes.. 

mph999's picture

Looking in scan I see

tape# / serial num / robot#

tape0 / 904N / changer 0
tape1 / 620D / changer 0
tape2 / 904N / changer 1
tape3 / 620D / changer 0
tape4 / 49VH /
tape5 / 49VH /

From scan I see that the serial numbers of the drives appear in the changers listed in scan as shown.

tape1 and 3 appear to have the same serial number so I suspect the drive is appearing twice
tape4 and 5 have same serial number, but this doesn't appear in the changers

Then I noticed the serial number of changer 0 and changer1 is the same.

So it seems that the some of the devices are appearing twice, and one library is still missing.

How is this all connected, scsi or via a SAN ?

I don't think its scan as there are no WWNs listed, but if it is you need a san administrator to sort out the zoning, which is a san activity to allow the servers to see different devices. Zoning is too complex to cover on this forum, and is not really a NBU forum task anyhow.

If it's scsi connected as I suspect, you need to sort out the connections, so that the server can see each device once, or if you want dual paths (which I've never seen with scsi) , then each device twice.

At the moment you have a mix, and it's not working properly.

The first question to ask then, how many paths from the server to each device should there be - I suspect just 1, but scan appears to be showing 2 for some of the devices as the serial numbers appear more than once.

Go and sort this out, so that device manager sees each device correctly. Until this is correct, NBU will never work.

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

what is Zoaning level and how do I check? 

Zoning is done by your SAN admins.

As per Martin's findings above, there ssems to be 2 paths zoned to the same library and tape drives.

Your SAN/storage admins need to fix this.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

baba20009's picture

I fixed this yesterday it had nothing to do with zoning since I zonned these two tape libraries myself and zonning did not get changed.

when I removed tape library 2 six months ago I documented the ports and last week I reconnected to the same ports

the problem was for some reason netbackup assign the same serial # to both tape libraries.

Steps I did yesterday around 4 pm to fix: all don in Gui since I am windows admin.

1 - Under the Media and Device Management, Devices, Robots, right click on the TLD(0)  and deleted the  robot (changer 0) that had the wrong Serial #.

2 - Stop and Start netbakcup services.

3 - Right click on Robots and created a "New" Changer TLD (0).  It created the the changer with correct serial #.

4- Ran the "Configure Storage Devices" ( I could not believe all two Robots with 4 drives all showing up green!!)

5- Ran inventory on TLD (0) tape library two.

6- backup ran at 6:00 PM all successful.

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

tpconfig -d

Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   HP.ULTRIUM4-SCSI.000 hcart  TLD(0)  DRIVE=1
      {4,0,4,0}                                                        UP
      {5,0,5,0}                                                        UP
1   HP.ULTRIUM4-SCSI.001 hcart  TLD(0)  DRIVE=2
      {4,0,1,0}                                                        UP
      {5,0,2,0}                                                        UP
2   HP.ULTRIUM4-SCSI.002 hcart  TLD(1)  DRIVE=1
      {4,0,2,0}                                                        UP
      {5,0,3,0}                                                        UP
3   HP.ULTRIUM4-SCSI.003 hcart  TLD(1)  DRIVE=2
      {4,0,3,0}                                                        UP
      {5,0,4,0}                                                        UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = {5,0,5,1}
  TLD(1)     SCSI coordinates = {5,0,3,1}

EMM Server = nbu1

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

vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
nbu1                                       656000    ACTIVE
dalnbu01                                   656000    DEACTIVATED

                                PENDING REQUESTS

                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM4-SCSI.000     No      No                     No        hcart
    nbu1                       {4,0,4,0}                            TLD
    nbu1                       {5,0,5,0}                            TLD

HP.ULTRIUM4-SCSI.001     No      No                     No        hcart
    nbu1                       {4,0,1,0}                            TLD
    nbu1                       {5,0,2,0}                            TLD

HP.ULTRIUM4-SCSI.002     No      No                     No        hcart
    nbu1                       {4,0,2,0}                            TLD
    nbu1                       {5,0,3,0}                            TLD

HP.ULTRIUM4-SCSI.003     No      No                     No        hcart
    nbu1                       {4,0,3,0}                            TLD
    nbu1                       {5,0,4,0}                            TLD

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

SCAN

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape7"
Passthru Name: "Tape7"
Volume Header: ""
Port: 4; Bus: 0; Target: 1; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU184849VH"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1007904N"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z3H9"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z3H9"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1007904N"
Drive 2 Serial Number      : "HU1926620D"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 4; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1926620D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 4; Bus: 0; Target: 4; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU10078YC0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer3"
Passthru Name: "Changer3"
Volume Header: ""
Port: 4; Bus: 0; Target: 4; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z37D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z37D"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU10078YC0"
Drive 2 Serial Number      : "HU184849VH"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape6"
Passthru Name: "Tape6"
Volume Header: ""
Port: 5; Bus: 0; Target: 2; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU184849VH"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 5; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1007904N"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer1"
Passthru Name: "Changer1"
Volume Header: ""
Port: 5; Bus: 0; Target: 3; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z3H9"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z3H9"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1007904N"
Drive 2 Serial Number      : "HU1926620D"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape5"
Passthru Name: "Tape5"
Volume Header: ""
Port: 5; Bus: 0; Target: 4; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU1926620D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 5; Bus: 0; Target: 5; LUN: 0
Inquiry    : "HP      Ultrium 4-SCSI  H68W"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "H68W"
Serial Number: "HU10078YC0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer2"
Passthru Name: "Changer2"
Volume Header: ""
Port: 5; Bus: 0; Target: 5; LUN: 1
Inquiry    : "HP      MSL G3 Series   7.80"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "7.80"
Serial Number: "MXA009Z37D"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   MXA009Z37D"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU10078YC0"
Drive 2 Serial Number      : "HU184849VH"
Flags : 0x0
Reason: 0x0
*******************************************************

Thanks guys for all your replies

mph999's picture

So running the wizard as suggested in my first post should have worked - odd.

And in my second or third post, I suggested to just delete things if you still had issues - I have sometimes seen 'old' confg cause problems with re-running the wizard (sometimes does/ sometimes doesn't)

"When the robot was removed for your testing, was it deleted from NBU, or just unplugged ? It could be worth deleting the robot from NBU config and re-ruinnng the wizard, having first made sure the robot can be seen correctly from the OS."

This makes no sense:

"the problem was for some reason netbackup assign the same serial # to both tape libraries."

NBU does NOT assign serial numbers.- it is given the serial numbers by the devices themselves.

What also doesn't make sense is why scan showed the two libraries with the same serial numbers - scan has nothing to do with NetBackup - you can delete all the devices and scan will still work - it simply sends scsi commands to the devices found in the OS, and what is displayed on the screen, apart from a little formatting, is what is sent back from the devices.  So if something is missing, it's because it either didn't get the scsi command, or was unable to respond/ respond correctly.
I'll prove it:
 
NBU Is stopped on my server - scan still works (just shows a single tape drive, no robot)
 
root@womble logs $ bpps -x
NB Processes
------------
 
 
MM Processes
------------
 
 
Shared Symantec Processes
-------------------------
    root 24199     1   0   Oct 16 ?           0:11 /opt/VRTSpbx/bin/pbx_exchange
 
root@womble logs $ scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t3l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 1-SCSI  E38W"
Vendor ID  : "HP      "
Product ID : "Ultrium 1-SCSI  "
Product Rev: "E38W"
Serial Number: "HU74D01591"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 1-SCSI  HU74D01591"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0

The main thing sometimes is to not worry too much when things are now working.

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION