Solved: Made no difference. I still

Katiebee · ‎12-02-2014

Hi all,

I have recently upgraded the tape library we use to do our weekly DR Vault from 2 to 4 tape drives, but I am having trouble getting the Vault process to use 4 tape drives simultaneously.

I have created the touch file VLT_MAXIMIZE_DRIVE_UTILIZATION_FOR_DISK in the Bin folder in the install location; I have checked that all of these drives are in the appropriate storage group, and that they all work. If I restart the Vault job, it is a different combination of drives that end up being used but it still only picks 2 out of the 4. Interestingly, if I try to run another vault job it will not use the two remaining drives but will advise that the resource limit has been reached (but this could be because the duplication lock cannot be assigned to the second job.)

In the Host properties the maximum vault jobs is set to 50, but I think this means the parent vault jobs rather than the number of concurrent batches for each vault.

The job advises it's doing 29 batches, 4 start but 2 of the spawned jobs advise they are awaiting resources, there are plenty of blank tapes in the library for it to use, the job even has one allocated, it shows >

awaiting resource MediaServer3-hcart-robot-tld-1 A pending request has been generated for this resource request.

Operator action may be required. Pending Action: No action.,

Media ID: DR0489, Barcode: DR0489, Density: hcart, Access Mode: Write,

Action Drive Name: N/A, Action Media Server: MediaServer3, Robot Number: N/A, Robot Type: NONE,

Volume Group: 000_00001_TLD, Action Acs: N/A, Action Lsm: N/A

In the above you can see the Storage unit resource that has been requested is MediaServer3, I have checked the other running batches and they all have different Storage unit resources requested so I don't think it's that? Is there somewhere something which is telling the vault to only process so much at a time as I am at a loss as to where else to look.

I am using Netbackup 7.5.0.6, the master server is Win 2003, as are 3 of the media servers, with one media server being Win 2008 Standard.

Any help would be appreciated

mph999 · ‎01-14-2015

Unless I've lost the plot, these two drives ... their serial numbers do not appear as listed in one of the robots.
Therefore NBU will be unable to work out that they are robotic.

Drive Name Drive006
Index 6
SCSI coordinates {5,0,28,0}
Type hcart
Status UP
SCSI Protection SR (Global)
Shared Access Yes
TLD(1) Definition DRIVE=1
Serial Number C38D27D000

Drive Name Drive009
Index 9
SCSI coordinates {5,0,31,0}
Type hcart
Status UP
SCSI Protection SR (Global)
Shared Access Yes
TLD(1) Definition DRIVE=4
Serial Number C38D27D00C

So, for example, from the scan output on RCH, one of the robots looks like this, which I think is TLD(1).

Inquiry : "QUANTUM Scalar i40-i80 172G"
Vendor ID : "QUANTUM "
Product ID : "Scalar i40-i80 "
Product Rev: "172G"
Serial Number: "QUANTUMD1H0031B11_LLA"
Number of Drives : 4
Number of Slots : 50
Number of Media Access Ports: 5
Drive 1 Serial Number : "HU1340YK5B"
Drive 2 Serial Number : "C38D27D004"
Drive 3 Serial Number : "C38D27D008"
Drive 4 Serial Number : "HU1310UY4M"

scan output is sent from the robot, so the robot is telling us it has x4 drives, but as you see, the serial numbers of the two drives I have listed are not there.

This is an issue on the library, the scan output is the result of a scsi command sent yto the library, ie. we ask, 'what drives do you have', and we seem to be getting back the wrong information.

The other possibility is that the robot info is correct, but the drives on the media server are reporting incorrect serial numbers, but I think this is less likely.

View solution in original post

RamNagalla · ‎12-02-2014

hopefully source images are in disk.

what is the max concurent drives for the STU MediaServer3-hcart-robot-tld-1 ? does it 2 or 4?

it should be 4 inorder to pick 4 drives for write operations...

Katiebee · ‎12-02-2014

Thanks for the quick response

If I look under the Storage unit groups in the Netbackup Admin console the drives in the i80 all have max concurrent as 4, the other library I use is set to 6 and all 6 drives are being used. The STU were previously set to 2 before we added the two further drives but is there anywhere else that I need to change this or anywhere I can check it is being picked up correctly?

Many thanks,

Katie

RamNagalla · ‎12-02-2014

does the newly added drives are with the same density..and LTO type?

could you post the below command output from MediaServer3

vmoprcmd -d

tpconfig -d

and how many storage units in GUI--> storage for MediaServer3 ?

Katiebee · ‎12-02-2014

Hi, Yes, same density and LTO type, as I said in the op the issue isn't affecting 2 specific drives, if I cancel the vault and start another then the two drives that are used are not necessarily the same two. I will have to post the outputs from the media server tomorrow as I am not in a position to get them now, but the media server which was requested in the above jobs had access to 10 tape drives in total if that is what your question was asking. Many thanks Katie

Marianne · ‎12-02-2014

What is listed in Destination Write Drives field in the Duplication tab of the Vault profile?

Handy NetBackup Links

watsons · ‎12-02-2014

One simple check, in your vault profile configuration -> "Duplication", what is the value of the "write drives"?

Katiebee · ‎12-03-2014

MediaServer

Today the vault seems to be hanging, 50% ish of the batches are completed but the otehr 50% are waiting for resources still.

My Vault profle uses the advanced settings for duplication, I have set up a STU allocation for each media server with one read and one write drive, so there are

I might try restarting it to see if it is the same STU which ends up waiting for resources.

Output from MediaServer3

C:\Documents and Settings\admin>tpconfig -d
Id DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   Drive000             hcart TLD(0) DRIVE=5
      {5,0,20,0}                                                       UP
      {2,0,20,0}                                                       UP
1   Drive001             hcart TLD(0) DRIVE=6
      {2,0,21,0}                                                       UP
      {5,0,21,0}                                                       UP
2   Drive002             hcart TLD(0) DRIVE=1
      {2,0,22,0}                                                       UP
      {5,0,22,0}                                                       UP
3   Drive004             hcart TLD(0) DRIVE=3
      {2,0,24,0}                                                       UP
      {5,0,24,0}                                                       UP
4   Drive005             hcart TLD(0) DRIVE=4
      {2,0,25,0}                                                       UP
      {5,0,25,0}                                                       UP
5   Drive003             hcart TLD(0) DRIVE=2
      {2,0,23,0}                                                       UP
      {5,0,23,0}                                                       UP
6   Drive006             hcart TLD(1) DRIVE=1
      {2,0,26,0}                                                       UP
      {5,0,26,0}                                                       UP
7   Drive007             hcart TLD(1) DRIVE=2
      {2,0,27,0}                                                       UP
      {5,0,27,0}                                                       UP
8   Drive008             hcart TLD(1) DRIVE=3
      {2,0,28,0}                                                       UP
      {5,0,28,0}                                                       UP
9   Drive009             hcart TLD(1) DRIVE=4
      {2,0,29,0}                                                       UP
      {5,0,29,0}                                                       UP

Currently defined robotics are:
TLD(0) robot control host = MasterServer-V
TLD(1) robot control host = MasterServer-V

EMM Server = MasterServer-v

C:\Documents and Settings\admin>vmoprcmd -d

PENDING REQUESTS

ReqId User RecMID ExtMID Density Mode Time Barcode VolGroup
192257651 DR0478 hcart Write 20:06 DR0478 000_00001_

DRIVE STATUS

Drv Type   Control User      Label RecMID ExtMID Ready   Wr.Enbl. ReqId
0 hcart    TLD               Yes   0960L4 0960L4   Yes     Yes        0
0 hcart    TLD               Yes   0960L4 0960L4   Yes     Yes        0
1 hcart    TLD               Yes   000738 000738   Yes     Yes        0
1 hcart    TLD               Yes   000738 000738   Yes     Yes        0
2 hcart    TLD               Yes   0958L4 0958L4   Yes     Yes        0
2 hcart    TLD               Yes   0958L4 0958L4   Yes     Yes        0
3 hcart    TLD               Yes   000169 000169   Yes     Yes        0
3 hcart    TLD               Yes   000169 000169   Yes     Yes        0
4 hcart    TLD               Yes   000699 000699   Yes     Yes        0
4 hcart    TLD               Yes   000699 000699   Yes     Yes        0
5 hcart    TLD               Yes   000972 000972   Yes     Yes        0
5 hcart    TLD               Yes   000972 000972   Yes     Yes        0
6 hcart    AVR                -                     No       -         0
6 hcart    AVR                -                     No       -         0
7 hcart    AVR                -                     No       -         0
7 hcart    AVR                -                     No       -         0
8 hcart    AVR                -                     No       -         0
8 hcart    AVR                -                     No       -         0
9 hcart    AVR                -                     No       -         0
9 hcart    AVR                -                     No       -         0

ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
0 Drive000              Yes      MediaServer3
0 Drive000              Yes      MediaServer3
1 Drive001              Yes      MediaServer5
1 Drive001              Yes      MediaServer5
2 Drive002              Yes      MediaServer1
2 Drive002              Yes      MediaServer1
3 Drive004              Yes      MediaServer1
3 Drive004              Yes      MediaServer1
4 Drive005              Yes      MediaServer1
4 Drive005              Yes      MediaServer1
5 Drive003              Yes      MediaServer3
5 Drive003              Yes      MediaServer3
6 Drive006              Yes      -
6 Drive006              Yes      -
7 Drive007              Yes      -
7 Drive007              Yes      -
8 Drive008              Yes      -
8 Drive008              Yes      -
9 Drive009              Yes      -
9 Drive009              Yes      -

Drives 000-005 are used for SLP duplications and all seem to be working fine, it's drives 006-009 which are in the i80 and are the ones I m trying to use for the vault process.

Thank you all for your ongoing help

Katie

Katiebee · ‎12-03-2014

This is the output for vmoprcmd -d from one of the media servers that was sucessfully writing to one of the drives, interestingly the control is showing at TLD as opposed to AVR on the media server which was pending.

Drv Type   Control User      Label RecMID ExtMID Ready   Wr.Enbl. ReqId
0 hcart    TLD               Yes   0960L4 0960L4   Yes     Yes        0
0 hcart    TLD               Yes   0960L4 0960L4   Yes     Yes        0
1 hcart    TLD               Yes   000738 000738   Yes     Yes        0
1 hcart    TLD               Yes   000738 000738   Yes     Yes        0
2 hcart    TLD               Yes   0958L4 0958L4   Yes     Yes        0
2 hcart    TLD               Yes   0958L4 0958L4   Yes     Yes        0
3 hcart    TLD               Yes   000169 000169   Yes     Yes        0
3 hcart    TLD               Yes   000169 000169   Yes     Yes        0
4 hcart    TLD               Yes   000699 000699   Yes     Yes        0
4 hcart    TLD               Yes   000699 000699   Yes     Yes        0
5 hcart    TLD               Yes   000972 000972   Yes     Yes        0
5 hcart    TLD               Yes   000972 000972   Yes     Yes        0
6 hcart    TLD                -                     No       -         0
6 hcart    TLD                -                     No       -         0
7 hcart    TLD                -                     No       -         0
7 hcart    TLD                -                     No       -         0
8 hcart    TLD                -                     No       -         0
8 hcart    TLD                -                     No       -         0
9 hcart    TLD                -                     No       -         0
9 hcart    TLD                -                     No       -         0

Katiebee · ‎12-03-2014

Edit: deleted comment as it was a duplicate of a previous one

RamNagalla · ‎12-03-2014

006-009 drives are showing in AVR meadia server where the jobs are penidng.. which is expected...

AVR mode indicates drives lost the communication with the robot and they can not be allocated to any jobs as long as they are in AVR move..

and the output of working one is Showing the TLD , and that is the reason they are working..

you need to fix the AVR mode drives inoder to pick them for read and write operations...

try restarting the litd and tlddd deamons on not working media server and see if they fix the AVR issue

Katiebee · ‎12-03-2014

Stupid question as I think I know the answer but will stopping and starting these deamons stop the communications with the drives 003 and 005?

Thanks

Katie

Marianne · ‎12-03-2014

Yes. Restarting services on this media server will affect all jobs and all drives on the media server.

This is a choice only you can make.

I am curious to know output of vmoprcmd on MasterServer-V....

Handy NetBackup Links

Katiebee · ‎12-04-2014

The output from the master is

PENDING REQUESTS

<NONE>

DRIVE STATUS

Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId
0 hcart TLD Yes 000916 000916 Yes Yes 0
0 hcart TLD Yes 000916 000916 Yes Yes 0
1 hcart TLD Yes 000672 000672 Yes Yes 0
1 hcart TLD Yes 000672 000672 Yes Yes 0
2 hcart TLD Yes 000003 000003 Yes Yes 0
2 hcart TLD Yes 000003 000003 Yes Yes 0
3 hcart TLD - No - 0
3 hcart TLD - No - 0
4 hcart TLD Yes 000913 000913 Yes Yes 0
4 hcart TLD Yes 000913 000913 Yes Yes 0
5 hcart TLD Yes 000800 000800 Yes Yes 0
5 hcart TLD Yes 000800 000800 Yes Yes 0
6 hcart TLD - No - 0
6 hcart TLD - No - 0
7 hcart TLD - No - 0
7 hcart TLD - No - 0
8 hcart TLD - No - 0
8 hcart TLD - No - 0
9 hcart TLD - No - 0
9 hcart TLD - No - 0

ADDITIONAL DRIVE STATUS

Drv DriveName Shared Assigned Comment
0 Drive000 Yes MediaServer5
0 Drive000 Yes MediaServer5
1 Drive001 Yes MediaServer1
1 Drive001 Yes MediaServer1
2 Drive002 Yes MediaServer1
2 Drive002 Yes MediaServer1
3 Drive004 Yes -
3 Drive004 Yes -
4 Drive005 Yes MediaServer2
4 Drive005 Yes MediaServer2
5 Drive003 Yes MediaServer1
5 Drive003 Yes MediaServer1
6 Drive006 Yes -
6 Drive006 Yes -
7 Drive007 Yes -
7 Drive007 Yes -
8 Drive008 Yes -
8 Drive008 Yes -
9 Drive009 Yes -
9 Drive009 Yes -

I have stopped and started ltid on MediaServer3 (this killed tldd so I didnt restart seperatly) and run vmoprcmd -d but this is shwoing the same as previously, the control type for drives 006-009 is AVR and not TLD.

Many thanks,

Katie

Katiebee · ‎12-04-2014

I've run scan for good measure on MediaServer3 and get the following output

************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
************************************************************
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. )
------------------------------------------------------------
Device Name : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 2; Bus: 0; Target: 20; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546000"
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: 2; Bus: 0; Target: 21; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546004"
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: 2; Bus: 0; Target: 22; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546090"
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: 2; Bus: 0; Target: 23; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546094"
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 : ""
Passthru Name: ""
Volume Header: ""
Port: 2; Bus: 0; Target: 23; LUN: 1
Inquiry : "ADIC Scalar i500 636G"
Vendor ID : "ADIC "
Product ID : "Scalar i500 "
Product Rev: "636G"
Serial Number: "ADICA0C0028629_LLA"
WWN : ""
WWN Id Type : 0
Device Identifier: "ADIC A0C0028629_LLA "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 6
Number of Slots : 109
Number of Media Access Ports: 18
Drive 1 Serial Number : "F09E546090"
Drive 2 Serial Number : "F09E546094"
Drive 3 Serial Number : "F09E546098"
Drive 4 Serial Number : "F09E54609C"
Drive 5 Serial Number : "F09E546000"
Drive 6 Serial Number : "F09E546004"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 2; Bus: 0; Target: 24; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546098"
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: 2; Bus: 0; Target: 25; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E54609C"
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 : "Tape6"
Passthru Name: "Tape6"
Volume Header: ""
Port: 2; Bus: 0; Target: 26; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D000"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : ""
Passthru Name: ""
Volume Header: ""
Port: 2; Bus: 0; Target: 26; LUN: 1
Inquiry : "QUANTUM Scalar i40-i80 172G"
Vendor ID : "QUANTUM "
Product ID : "Scalar i40-i80 "
Product Rev: "172G"
Serial Number: "QUANTUMD1H0031B11_LLA"
WWN : ""
WWN Id Type : 0
Device Identifier: "QUANTUM D1H0031B11_LLA "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 4
Number of Slots : 50
Number of Media Access Ports: 5
Drive 1 Serial Number : "HU1340YK5B"
Drive 2 Serial Number : "C38D27D004"
Drive 3 Serial Number : "C38D27D008"
Drive 4 Serial Number : "HU1310UY4M"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape7"
Passthru Name: "Tape7"
Volume Header: ""
Port: 2; Bus: 0; Target: 27; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D004"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape8"
Passthru Name: "Tape8"
Volume Header: ""
Port: 2; Bus: 0; Target: 28; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D008"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape9"
Passthru Name: "Tape9"
Volume Header: ""
Port: 2; Bus: 0; Target: 29; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D00C"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape10"
Passthru Name: "Tape10"
Volume Header: ""
Port: 5; Bus: 0; Target: 20; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546000"
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 : "Tape11"
Passthru Name: "Tape11"
Volume Header: ""
Port: 5; Bus: 0; Target: 21; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546004"
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 : "Tape12"
Passthru Name: "Tape12"
Volume Header: ""
Port: 5; Bus: 0; Target: 22; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546090"
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 : "Tape13"
Passthru Name: "Tape13"
Volume Header: ""
Port: 5; Bus: 0; Target: 23; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546094"
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 : ""
Passthru Name: ""
Volume Header: ""
Port: 5; Bus: 0; Target: 23; LUN: 1
Inquiry : "ADIC Scalar i500 636G"
Vendor ID : "ADIC "
Product ID : "Scalar i500 "
Product Rev: "636G"
Serial Number: "ADICA0C0028629_LLA"
WWN : ""
WWN Id Type : 0
Device Identifier: "ADIC A0C0028629_LLA "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 6
Number of Slots : 109
Number of Media Access Ports: 18
Drive 1 Serial Number : "F09E546090"
Drive 2 Serial Number : "F09E546094"
Drive 3 Serial Number : "F09E546098"
Drive 4 Serial Number : "F09E54609C"
Drive 5 Serial Number : "F09E546000"
Drive 6 Serial Number : "F09E546004"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape14"
Passthru Name: "Tape14"
Volume Header: ""
Port: 5; Bus: 0; Target: 24; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E546098"
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 : "Tape15"
Passthru Name: "Tape15"
Volume Header: ""
Port: 5; Bus: 0; Target: 25; LUN: 0
Inquiry : "HP Ultrium 4-SCSI H63Z"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "H63Z"
Serial Number: "F09E54609C"
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 : "Tape16"
Passthru Name: "Tape16"
Volume Header: ""
Port: 5; Bus: 0; Target: 26; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D000"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : ""
Passthru Name: ""
Volume Header: ""
Port: 5; Bus: 0; Target: 26; LUN: 1
Inquiry : "QUANTUM Scalar i40-i80 172G"
Vendor ID : "QUANTUM "
Product ID : "Scalar i40-i80 "
Product Rev: "172G"
Serial Number: "QUANTUMD1H0031B11_LLA"
WWN : ""
WWN Id Type : 0
Device Identifier: "QUANTUM D1H0031B11_LLA "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 4
Number of Slots : 50
Number of Media Access Ports: 5
Drive 1 Serial Number : "HU1340YK5B"
Drive 2 Serial Number : "C38D27D004"
Drive 3 Serial Number : "C38D27D008"
Drive 4 Serial Number : "HU1310UY4M"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape17"
Passthru Name: "Tape17"
Volume Header: ""
Port: 5; Bus: 0; Target: 27; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D004"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape18"
Passthru Name: "Tape18"
Volume Header: ""
Port: 5; Bus: 0; Target: 28; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D008"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape19"
Passthru Name: "Tape19"
Volume Header: ""
Port: 5; Bus: 0; Target: 29; LUN: 0
Inquiry : "HP Ultrium 5-SCSI Y6AZ"
Vendor ID : "HP "
Product ID : "Ultrium 5-SCSI "
Product Rev: "Y6AZ"
Serial Number: "C38D27D00C"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0

I also ran this on another media server which is writing to the i80 drives and the output is the same apart from the lines DeviceIoControl() error on bus 0, target 27, lun 1 (2:The system cannot
file specified. ) do not appear.

many thanks,

Katie

Marianne · ‎12-04-2014

Have you checked Event Viewer System log on MediaServer3 for errors?

When last was this server rebooted?

Handy NetBackup Links

Katiebee · ‎12-04-2014

Its been rebooted in the last week, I've been patching the Windows boxes so have gracefully shutdown the whole netbackup envirnoment a couple of times.

I have had a look in Event Viewer and there are a couple of errors, its not full of them though:

Event Type:   Error
Event Source:   NetBackup TLD Daemon
Event Category:   None
Event ID:   7823
Date:       04/12/2014
Time:       13:37:29
User:       N/A
Computer:   APPNBU3
Description:
TLD(0) [1108] Drive 4 (device 4) has not become ready. Last status: The requested resource is in use.

I think the above is a normal one relating to the library which is working? Most are like the above, there is only one more today:

Event Type:   Error
Event Source:   NetBackup
Event Category:   None
Event ID:   2753
Date:       04/12/2014
Time:       11:23:32
User:       N/A
Computer:   APPNBU3
Description:
ltid can not be started while resources are assigned to the host.

I am going to reboot the whole lot and see if I get any more errors.

thanks for staying with me on this issue :)

Katie

Katiebee · ‎12-04-2014

After rebooting everything I can see the below error on MediaServer3

EMM interface initialization failed, status = 334

But when I checked other media servers which will use the drives okay they also have this error.

Tried a vault and still only 2 of the media servers are able to successfully request the tape drive resource.

Does anyone have any other ideas?

Many thanks,

Katie

Katiebee · ‎12-09-2014

I'm going to try starting from scratch with the i80 as it's still not working for two of the media servers, which makes a big difference.

I will post an update later.

Katie

Katiebee · ‎12-09-2014

Made no difference. I still get the drives showing as AVR controlled:

6 hcart AVR - No - 0
6 hcart AVR - No - 0
7 hcart AVR - No - 0
7 hcart AVR - No - 0
8 hcart AVR - No - 0
8 hcart AVR - No - 0
9 hcart AVR - No - 0
9 hcart AVR - No - 0

when I run vmoprcmd -d on mediaserver2 and 3, but they are correctly shown as TLD on the other media server and master.

When I go to the Media and Device Management > Devices > Robots I can only see the robot in the i80 having the two working media servers as hosts. I have tried to add the other two missing servers but when I do selecting Robot control is handled by a remote host and putting the correct name in the Robot Control Host field I just get an error advising that it cannot process the command as the robot number is already in use(21)

Do I need to use tpconfig -add on the media server itself? When I do tpconfig -l on the media server it does show that it can see the library and the robot?

Device Robot Drive       Robot                    Drive     Device
Type     Num Index Type DrNum Status Comment    Name      Path
robot      0    -    TLD    -       - -          -         MasterServer-V
drive    -    0 hcart    5      UP -          Drive000 {2,0,1,0}
drive    -    0 hcart    5      UP -          Drive000 {4,0,1,0}
drive    -    1 hcart    6      UP -          Drive001 {2,0,2,0}
drive    -    1 hcart    6      UP -          Drive001 {4,0,2,0}
drive    -    2 hcart    1      UP -          Drive002 {2,0,3,0}
drive    -    2 hcart    1      UP -          Drive002 {4,0,3,0}
drive    -    3 hcart    3      UP -          Drive004 {2,0,7,0}
drive    -    3 hcart    3      UP -          Drive004 {4,0,7,0}
drive    -    4 hcart    4      UP -          Drive005 {2,0,8,0}
drive    -    4 hcart    4      UP -          Drive005 {4,0,8,0}
drive    -    5 hcart    2      UP -          Drive003 {2,0,4,0}
drive    -    5 hcart    2      UP -          Drive003 {4,0,6,0}
robot      1    -    TLD    -       - -          -         MasterServer-V
drive    -    6 hcart    2      UP -          Drive007 {2,0,10,0}
drive    -    6 hcart    2      UP -          Drive007 {4,0,10,0}
drive    -    7 hcart    3      UP -          Drive008 {2,0,11,0}
drive    -    7 hcart    3      UP -          Drive008 {4,0,11,0}
drive    -    8 hcart    4      UP -          Drive009 {2,0,12,0}
drive    -    8 hcart    4      UP -          Drive009 {4,0,12,0}
drive    -    9 hcart    1      UP -          Drive006 {2,0,9,0}
drive    -    9 hcart    1      UP -          Drive006 {4,0,9,0}

I know I must be doing something wrong but I really don't know what

If anyone can think of anything else which might help I would really appricate it

Thanks,

Katie

VOX

Vault only using 2 out of 4 drives