NBU keep mounting tape forever

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

NBU keep mounting tape forever

clnunes
Hi guys,

      I'm a newbie in MHVTL and after thousands of tries and read thought the forum I decide ask you gurus. :)

                                                            Here is my environment:

      Running on VMware workstation

      I installed an CentOS 5.7 with the latest MHVTL source and everything went very well and seems to be working as it supposed to.

      I installed an Windows 2008 x64 and NBU 7.1. Windows recognizes all the hardware and I managed to install the device drivers with no problem.



      When I try to configure the Storage Devices I got the screens below.
   
      The robot and drives are found.


   
  The models and firmwares are showed as configured but it says that the drives has limitations.



If I click on properties it shows the info below




So I click Next and the screen below come up



Since it is an Drag and Drop, I dragged the drives to the robot and continue configuring the NBU. After finish the Storage Configuration this is what I have in NBU.



It seems to be ok too. I performed an invetory on the robot and it worked too.



So my pools are as show below.



After that I created a simple job to backup one single folder in the NBU server. The job starts and stay mounting the tape forever.



The job Details are like this.


 
Can you figure out why the tape never finishes to mount?

Here are my MHVTL and TGTD cong files and daemon outputs.

cat /etc/mhvtl/device.conf

VERSION: 5

# VPD page format:
# <page #> <Length> <x> <x+1>... <x+n>
# NAA format is an 8 hex byte value seperated by ':'
# Note: NAA is part of inquiry VPD 0x83
#
# Each 'record' is separated by one (or more) blank lines.
# Each 'record' starts at column 1
# Serial num max len is 10.
# Compression: factor X enabled 0|1
#     Where X is zlib compression factor        1 = Fastest compression
#                                               9 = Best compression
#     enabled 0 == off, 1 == on

Library: 10 CHANNEL: 03 TARGET: 01 LUN: 03
 Vendor identification: HP
 Product identification: MSL6000 Series
 Product revision level: 0520
 Unit serial number: USX604009T
 NAA: 10:22:33:44:ab:03:01:01
 fifo: /var/tmp/mhvtl

Drive: 11 CHANNEL: 03 TARGET: 01 LUN: 01
 Library ID: 10 Slot: 01
 Vendor identification: HP
 Product identification: Ultrium 2-SCSI
 Product revision level: F6AW
 Unit serial number: HU10606DUE
 NAA: 10:22:33:44:ab:03:01:02
 Compression: factor 1 enabled 1
 Compression type: lzo
 fifo: /var/tmp/mhvtl

Drive: 12 CHANNEL: 03 TARGET: 01 LUN: 02
 Library ID: 10 Slot: 02
 Vendor identification: HP
 Product identification: Ultrium 2-SCSI
 Product revision level: F6AW
 Unit serial number: HU10606DUF
 NAA: 10:22:33:44:ab:03:01:03
 Compression: factor 1 enabled 1
 Compression type: lzo
 fifo: /var/tmp/mhvtl


lsscsi -g

[0:0:0:0]    disk    VMware,  VMware Virtual S 1.0   /dev/sda  /dev/sg0
[1:3:1:1]    tape    HP       Ultrium 2-SCSI   F6AW  /dev/st0  /dev/sg1
[1:3:1:2]    tape    HP       Ultrium 2-SCSI   F6AW  /dev/st1  /dev/sg2
[1:3:1:3]    mediumx HP       MSL6000 Series   0520  -         /dev/sg3



cat library_contents.10

Drive 1:
Drive 2:

Picker 1:

MAP 1:
MAP 2:
MAP 3:
MAP 4:

# Slot 1 - ?, no gaps
# Slot N: [barcode]
# [barcode]
# a barcode is comprised of three fields: [Leading] [identifier] [Trailing]
# Leading "CLN" -- cleaning tape
# Leading "W" -- WORM tape
# Leading "NOBAR" -- will appear to have no barcode
# If the barcode is at least 8 character long, then the last two characters are Trailing
# Trailing "S3" - SDLT600
# Trailing "X4" - AIT-4
# Trailing "L1" - LTO 1, "L2" - LTO 2, "L3" - LTO 3, "L4" - LTO 4, "L5" - LTO 5
# Training "LT" - LTO 3 WORM, "LU" LTO 4 WORM, "LV" LTO 5 WORM
# Trailing "TA" - T10000+
# Trailing "JA" - 3592+
# Trailing "JB" - 3592E05+
# Trailing "JW" - WORM 3592+
# Trailing "JX" - WORM 3592E05+
#
Slot 0: CLN101L2
Slot 1: E01001L2
Slot 2: E01002L2
Slot 3: E01003L2
Slot 4: E01004L2
Slot 5: E01005L2
Slot 6: E01006L2
Slot 7: E01007L2
Slot 8: E01008L2
Slot 9: E01009L2
Slot 10: E01010L2
Slot 11: E01011L2
Slot 12: E01012L2
Slot 13: E01013L2
Slot 14: E01014L2
Slot 15: E01015L2
Slot 16: E01016L2
Slot 17: E01017L2
Slot 18: E01018L2
Slot 19: E01019L2
Slot 20: E01020L2
Slot 21: E01021L2
Slot 22: E01022L2
Slot 23: E01023L2
Slot 24:
Slot 25:
Slot 26:
Slot 27:
Slot 28:

cat /etc/tgt/targets.conf

default-driver iscsi

<target iqn.2011-02.com.ceva:vtl:1:0:0:0>
        <backing-store /dev/sg1>
                device-type pt
                bs-type sg
                vendor_id "HP      "
                product_id "Ultrium 2-SCSI  "
                product_rev "F6AW"
                scsi_sn "HU10606DUE"
                lun 1
        </backing-store>

        <backing-store /dev/sg2>
                device-type pt
                bs-type sg
                vendor_id "HP      "
                product_id "Ultrium 2-SCSI  "
                product_rev "F6AW"
                scsi_sn "HU10606DUF"
                lun 2
        </backing-store>

        <backing-store /dev/sg3>
                device-type pt
                removable 1
                bs-type sg
                vendor_id "HP      "
                product_id "MSL6000 Series  "
                product_rev "0520"
                scsi_sn "USX604009T"
                lun 3
        </backing-store>

</target>

 tgt-admin -s

Target 1: iqn.2011-02.com.ceva:vtl:1:0:0:0
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
        I_T nexus: 2
            Initiator: iqn.1991-05.com.microsoft:winnbu
            Connection: 1
                IP Address: 192.168.75.130
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00010000
            SCSI SN: beaf10
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags:
        LUN: 1
            Type: passthrough
            SCSI ID: IET     00010001
            SCSI SN: HU10606DUE
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg1
            Backing store flags:
        LUN: 2
            Type: passthrough
            SCSI ID: IET     00010002
            SCSI SN: HU10606DUF
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg2
            Backing store flags:
        LUN: 3
            Type: passthrough
            SCSI ID: IET     00010003
            SCSI SN: USX604009T
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: Yes
            Readonly: No
            Backing store type: sg
            Backing store path: /dev/sg3
            Backing store flags:
    Account information:
    ACL information:
        ALL

mtx -f /dev/sg3 status

  Storage Changer /dev/sg3:2 Drives, 33 Slots ( 4 Import/Export )
Data Transfer Element 0:Empty
Data Transfer Element 1:Empty
      Storage Element 1:Full :VolumeTag=E01001L2
      Storage Element 2:Full :VolumeTag=E01002L2
      Storage Element 3:Full :VolumeTag=E01003L2
      Storage Element 4:Full :VolumeTag=E01004L2
      Storage Element 5:Full :VolumeTag=E01005L2
      Storage Element 6:Full :VolumeTag=E01006L2
      Storage Element 7:Full :VolumeTag=E01007L2
      Storage Element 8:Full :VolumeTag=E01008L2
      Storage Element 9:Full :VolumeTag=E01009L2
      Storage Element 10:Full :VolumeTag=E01010L2
      Storage Element 11:Full :VolumeTag=E01011L2
      Storage Element 12:Full :VolumeTag=E01012L2
      Storage Element 13:Full :VolumeTag=E01013L2
      Storage Element 14:Full :VolumeTag=E01014L2
      Storage Element 15:Full :VolumeTag=E01015L2
      Storage Element 16:Full :VolumeTag=E01016L2
      Storage Element 17:Full :VolumeTag=E01017L2
      Storage Element 18:Full :VolumeTag=E01018L2
      Storage Element 19:Full :VolumeTag=E01019L2
      Storage Element 20:Full :VolumeTag=E01020L2
      Storage Element 21:Full :VolumeTag=E01021L2
      Storage Element 22:Full :VolumeTag=E01022L2
      Storage Element 23:Full :VolumeTag=E01023L2
      Storage Element 24:Empty
      Storage Element 25:Empty
      Storage Element 26:Empty
      Storage Element 27:Empty
      Storage Element 28:Empty
      Storage Element 29:Empty
      Storage Element 30 IMPORT/EXPORT:Empty
      Storage Element 31 IMPORT/EXPORT:Empty
      Storage Element 32 IMPORT/EXPORT:Empty
      Storage Element 33 IMPORT/EXPORT:Empty

 mtx -f /dev/sg3 load 2 1
 mtx -f /dev/sg3 status


  Storage Changer /dev/sg3:2 Drives, 33 Slots ( 4 Import/Export )
Data Transfer Element 0:Empty
Data Transfer Element 1:Full (Storage Element 2 Loaded):VolumeTag = E01002L2
      Storage Element 1:Full :VolumeTag=E01001L2
      Storage Element 2:Empty
      Storage Element 3:Full :VolumeTag=E01003L2
      Storage Element 4:Full :VolumeTag=E01004L2
      Storage Element 5:Full :VolumeTag=E01005L2
      Storage Element 6:Full :VolumeTag=E01006L2
      Storage Element 7:Full :VolumeTag=E01007L2
      Storage Element 8:Full :VolumeTag=E01008L2
      Storage Element 9:Full :VolumeTag=E01009L2
      Storage Element 10:Full :VolumeTag=E01010L2
      Storage Element 11:Full :VolumeTag=E01011L2
      Storage Element 12:Full :VolumeTag=E01012L2
      Storage Element 13:Full :VolumeTag=E01013L2
      Storage Element 14:Full :VolumeTag=E01014L2
      Storage Element 15:Full :VolumeTag=E01015L2
      Storage Element 16:Full :VolumeTag=E01016L2
      Storage Element 17:Full :VolumeTag=E01017L2
      Storage Element 18:Full :VolumeTag=E01018L2
      Storage Element 19:Full :VolumeTag=E01019L2
      Storage Element 20:Full :VolumeTag=E01020L2
      Storage Element 21:Full :VolumeTag=E01021L2
      Storage Element 22:Full :VolumeTag=E01022L2
      Storage Element 23:Full :VolumeTag=E01023L2
      Storage Element 24:Empty
      Storage Element 25:Empty
      Storage Element 26:Empty
      Storage Element 27:Empty
      Storage Element 28:Empty
      Storage Element 29:Empty
      Storage Element 30 IMPORT/EXPORT:Empty
      Storage Element 31 IMPORT/EXPORT:Empty
      Storage Element 32 IMPORT/EXPORT:Empty
      Storage Element 33 IMPORT/EXPORT:Empty

mtx -f /dev/sg3 inquiry

Product Type: Medium Changer
Vendor ID: 'HP      '
Product ID: 'MSL6000 Series  '
Revision: '0520'
Attached Changer: No

mtx -f /dev/sg1 inquiry

Product Type: Tape Drive
Vendor ID: 'HP      '
Product ID: 'Ultrium 2-SCSI  '
Revision: 'F6AW'
Attached Changer: No

mtx -f /dev/sg1 status

mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=yes
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Residual = 00 00 00 00
mtx: Request Sense: Additional Sense Code = 20
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
READ ELEMENT STATUS Command Failed

mtx -f /dev/sg2 inquiry

Product Type: Tape Drive
Vendor ID: 'HP      '
Product ID: 'Ultrium 2-SCSI  '
Revision: 'F6AW'
Attached Changer: No

mtx -f /dev/sg2 status

mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=yes
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Residual = 00 00 00 00
mtx: Request Sense: Additional Sense Code = 20
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
READ ELEMENT STATUS Command Failed

Please, help me to find what is wrong. If any other information is needed please, just ask.
Thank you
Cris

Reply | Threaded
Open this post in threaded view
|

Re: NBU keep mounting tape forever

Mark Harvey
Administrator
First off, many thanks for the details. Great problem report !

When using the device config wiArd, and you get 'Limitations' are seen, stop right there and resolve this.

The fix is to look at your external_mappings file and update the robot type in device.conf to suit.

Confirm using 'volmgr\bin\scan -changer' or the wizard..

The drives should then be part of the library and not show  as standalone.

Cheers
Mark
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: NBU keep mounting tape forever

clnunes
Hi Mark,

     Thanks for you answer.
     Could you give a little bit more details on it? I try to find (local
and google) the external mappings file for NBU 7 but no joy. The
device.conf you are referring to is the one for MHVTL, right?
    BTW the MHVTL HW info I got from a physical HP MSL 6000 (serial number/firmware/all info)

Cheers
Cris
Reply | Threaded
Open this post in threaded view
|

Re: NBU keep mounting tape forever

Mark Harvey
Administrator
Correct on both accounts.

The device_mappings.txt file (loaded into EMM for runtime use), but
lives on master server in /usr/openv/var/global (netbackup\var\global\
on Win). Newer versions of device_mappings is released from time to
time to support/describe new hardware - rather than the info being
hard-coded into NetBackup itself.

The problem is with NBU needing to 'understand' the SCSI inquiry
string rather than a mhvtl issue per-say

 mhvtl & NetBackup will work correctly with any changer device with a :
LIBRARY_SERIALIZATION=2

Hope this helps a little.

Cheers
Mark

On Thu, Mar 1, 2012 at 6:10 AM, clnunes [via MHVTL - Linux Virtual
Tape Library - Community Forums]
<[hidden email]> wrote:

> Hi Mark,
>
>      Thanks for you answer.
>      Could you give a little bit more details on it? I try to find (local
> and google) the external mappings file for NBU 7 but no joy. The device.conf
> you are referring to is the one for MHVTL, right?
>
> Cheers
> Cris
>
>
> 2012/2/29 Mark Harvey [via MHVTL - Linux Virtual Tape Library - Community
> Forums] <[hidden email]>
>>
>> First off, many thanks for the details. Great problem report !
>>
>> When using the device config wiArd, and you get 'Limitations' are seen,
>> stop right there and resolve this.
>>
>> The fix is to look at your external_mappings file and update the robot
>> type in device.conf to suit.
>>
>> Confirm using 'volmgr\bin\scan -changer' or the wizard..
>>
>> The drives should then be part of the library and not show  as standalone.
>>
>> Cheers
>> Mark
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/NBU-keep-mounting-tape-forever-tp3787713p3788245.html
>> To unsubscribe from NBU keep mounting tape forever, click here.
>> NAML
>
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/NBU-keep-mounting-tape-forever-tp3787713p3788302.html
> To start a new topic under MHVTL - Linux Virtual Tape Library - Community
> Forums, email [hidden email]
> To unsubscribe from MHVTL - Linux Virtual Tape Library - Community Forums,
> click here.
> NAML
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: NBU keep mounting tape forever

clnunes
Hey Mark,

     I tried to find a new device_mappings.txt from Symantec and couldn't. So I open the one on my master server and found this:
    
[CHANGER:HP MSL6000]
VENDOR_ID=HP
PRODUCT_ID=MSL6000
ROBOT_TYPE=8
LIBRARY_SERIALIZATION=3
COMPATIBILITY_TAG=4194305
NO_MAGAZINE_SENSE=8302
UNKNOWN_BARCODE_SENSE=8309

[DRIVE:NetBackup HCART2]
VENDOR_ID=HP
PRODUCT_ID=Ultrium 2
DRIVE_TYPE=10
 
        I tried to change the devices.conf to match the PRODUCT_ID for the library and the tape and with the changed version the Windows drivers didn't install and none were found by the NBU in the Configuration Wizard process.

        So I changed back the device.conf to what it was before and, taking your comment about the serialization, I changed the number 3 to number 2 on "LIBRARY_SERIALIZATION=3" and after a bpdown & bpup the NetBackup Device Manager starts and when I run the NBU Configuration Wizard process the service stops with no error message, not even in the Event Viewer.
        It is probably because the file digest changes.

        One interest thing i found is that the device_mapping.txt file which came on NBU 7.1 default installation has the following line:

           ====>        #  VERSION INFO:  This file is for use with NetBackup version(s) 5.0,5.1

        Question:

         Since I can "manage" the Library/Tapes/Media using the mt/mtx commands in the linux shell, the problems I'm facing on Windows box could be related to iSCSI protocol/implementation?

Cheers
Cris