Centos 6.0 + MHVTL + Data Protector 6.11 working OK.

[lsonzogni]

Hello people.
     This is my test config and is working fine.

- CentOS Linux release 6.0 (Final)
- Linux wilvtl1 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux
- OB2-CORE-A.06.11-1.x86_64
- OB2-DA-A.06.11-1.x86_64
- OB2-MA-A.06.11-1.x86_64
- MHVTL 0.18.17
- Mhvtl Web Console Build: 1.0.1-5e17122

/etc/mhvtl/devices.conf
Library: 40 CHANNEL: 2 TARGET: 00 LUN: 00
 Vendor identification: QUANTUM
 Product identification: PX720
 Product revision level: 0029
 Unit serial number: 60000040
 NAA: 40:11:22:33:ab:2:00:00

Drive: 41 CHANNEL: 2 TARGET: 00 LUN: 01
 Library ID: 40 Slot: 01
 Vendor identification: QUANTUM
 Product identification: DLT-S4
 Product revision level: 0A0A
 Unit serial number: 60000041
 NAA: 40:11:22:33:ab:2:00:01
 Compression: factor 1 enabled 1

Drive: 42 CHANNEL: 2 TARGET: 00 LUN: 2
 Library ID: 40 Slot: 2
 Vendor identification: QUANTUM
 Product identification: DLT-S4
 Product revision level: 0A0A
 Unit serial number: 60000042
 NAA: 40:11:22:33:ab:2:00:2
 Compression: factor 1 enabled 1

/etc/mhvtl/library_contents.40
Drive1:
Drive2:

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

Picker 1:

Slot 1: QUT001S4
Slot 2: QUT002S4
Slot 3: QUT003S4
Slot 4: QUT004S4
Slot 5: QUT005S4
Slot 6: QUT006S4
Slot 7: QUT007S4
Slot 8: QUT008S4
Slot 9: QUT009S4
Slot 10: QUT010S4
Slot 11: QUT011S4
Slot 12: QUT012S4
Slot 13: QUT013S4
Slot 14: QUT014S4
Slot 15: QUT015S4
Slot 16: QUT016S4
Slot 17: QUT017S4
Slot 18: QUT018S4
Slot 19: QUT019S4
Slot 20: CLN020S4

In Data Protector console, just "Autoconfigure devices"

[nia]

I have noticed that you have used the Web GUI to create this config .. Cool .. I am glad it worked for you  

-nia

[lsonzogni]

yeap !!.

Right now updated to Web Console Build: 1.0.1-f2bce52  using "Live Update"--> "Check for Updates"  buttons in the same Web GUI.

MHVTL 1.0.1 was updated using mhvtl-1.0-1.x86_64.rpm and mhvtl-2011-09-11.tgz (builds mhvtl-1.0-0). Just follow the instructions on http://sites.google.com/site/linuxvtl2/home#vtl-getting-started

Works like a charm

[tahrens]

I have tried similar config, but Data Protector suffers from not reading the device serial number from the library . It's OK when I manually configure position of the drives in the library.

/opt/omni # lbin/devbra -list

device: MEDIA CHANGER; host: "localhost"
port: 0; path: 0; target: 0; lun: 0; Path: "/dev/sg6"
Vendor: "STK"; product: "L80"; revision: "0102"; serial: "47111"
Description: "StorageTek L80 Tape Library"
presuming drives of type: "LTO: HP Ultrium drive"
S1 = 1024; Sn = 40; D1 = 1; Dn = 4; T1 = 256; Tn = 1; X1 = 512; Xn = 4
Drive 0 serial: "N/A"
Drive 1 serial: "N/A"
Drive 2 serial: "N/A"
Drive 3 serial: "N/A"

device: DRIVE; host: "localhost"
port: 0; path: 0; target: 0; lun: 0; Path: "/dev/nst1"
Vendor: "HP"; product: "Ultrium 4-SCSI"; revision: "0102"; serial: "47113"
Description: "HP LTO4 Drive"
device type: "LTO: HP Ultrium drive"

device: DRIVE; host: "localhost"
port: 0; path: 0; target: 0; lun: 0; Path: "/dev/nst0"
Vendor: "HP"; product: "Ultrium 4-SCSI"; revision: "0102"; serial: "47112"
Description: "HP LTO4 Drive"
device type: "LTO: HP Ultrium drive"

[Mark Harvey]

Can I ask you to change the robot type (/etc/mhvtl/device.conf) of the robot from STK / L80 to a  "Vendor identification: QUANTUM, Product identification: PX720 " and re-test the 'lbin/devbbra -list command please... (and advise of the outcome).

I know NetBackup only correctly detects the serial number of drives if the Vendor/Product identification are limited to types in the /usr/openv/var/local/device_mappings.txt with the "LIBRARY_SERIALIZATION=2"
e.g.

[CHANGER:STK L180]
VENDOR_ID=STK
PRODUCT_ID=L180
ROBOT_TYPE=8
LIBRARY_SERIALIZATION=2
COMPATIBILITY_TAG=4194305
MAILSLOT_DELAY=30
VENDOR_SENSE_ORDINAL=3
BARCODE_DETECTION=1

The Quantum PX720 is defined differently in NetBackup...
e.g.

[CHANGER:Quantum PX720]
VENDOR_ID=QUANTUM
PRODUCT_ID=PX720
ROBOT_TYPE=8
LIBRARY_SERIALIZATION=3
COMPATIBILITY_TAG=4195329
BARCODE_DETECTION=1
DRIVE_NEEDS_CLEANING_SENSE=8001,8002

Note: Until I get around to introducing library personality modules, it may be the work around is to document types that work with backup software.

Thanks
Mark