HP StorageWorks MSL2024 and HP LTO4 Ultrium 1840 drive with bacula 2.2.5/2.2.6
Hi all!
I can confirm that a HP StorageWorks MSL2024 and HP LTO4 Ultrium 1840 drive works flawlessly under Debian 4.0 etch with mtx 1.2.17rel-2 and Bacula 1.3.8/2.2.5/2.2.6.
Library/Tape robot: HP StorageWorks MSL2024 (HP part number: AJ033A) [ Product link ]
Drive inside: HP LTO4 Ultrium 1840
Capacity of a single tape: up to 800 GB native or 1,6 TB compressed (2:1 ratio)
Number of slots in library: 24
Library capacity: 19,2 TB native or 38,4 TB compressed (2:1 ratio)
Connection: U320 SCSI (legacy SCSI, not SAS!)
SCSI-HBA used: HP SC11Xe (HP part number: 412911-B21)
Here a short report like suggested at http://mtx.opensource-sw.net/contrib.php:
>uname -svrp Linux 2.6.23.1-custom #1 SMP Thu Dec 6 15:06:41 CET 2007 unknown > mtx --version mtx version 1.2.17rel > loaderinfo -f /dev/sg3 Product Type: Medium Changer Vendor ID: 'HP ' Product ID: 'MSL G3 Series ' Revision: '3.40' Attached Changer: No Bar Code Reader: Yes EAAP: Yes Number of Medium Transport Elements: 1 Number of Storage Elements: 24 Number of Import/Export Element Elements: 0 Number of Data Transfer Elements: 1 Transport Geometry Descriptor Page: Yes Invertable: No Device Configuration Page: Yes Can Transfer: Yes
A more detailed report:
Hi all!
The HP StorageWorks MSL2024 (HP product number AJ033A, Product link) works like a charm under Debian 4.0 with mtx 1.2.17rel-2 and Bacula 1.3.8/2.2.5/2.2.6.
The Server is nothing extraordinary, it's a 3U high machine from a local dealer with a PCI-Express-Port for the HBA.
To connect the autoloader to the backup-server a U320 SCSI-HBA (legacy SCSI, not SAS) "HP SC11Xe" (HP part number: 412911-B21) is used.
The driver is used for the HBA is the "LSI Logic" @ monolithic kernel 2.6.23.1.
Following kernel Options are activated:
[*] LSI Logic New Generation RAID Device Drivers <*> LSI Logic Management Module (New Driver) <*> LSI Logic MegaRAID Driver (New Driver) <*> LSI Logic Legacy MegaRAID Driver
Here the part of the "dmesg":
SCSI Media Changer driver v0.25
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.05
ACPI: PCI Interrupt 0000:0b:08.0[A] -> GSI 16 (level, low) -> IRQ 16
mptbase: Initiating ioc0 bringup
ioc0: LSI53C1020A A1: Capabilities={Initiator,Target}
scsi1 : ioc0: LSI53C1020A A1, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=16
scsi 1:0:4:0: Sequential-Access HP Ultrium 4-SCSI B23W PQ: 0 ANSI: 5
target1:0:4: Beginning Domain Validation
target1:0:4: Ending Domain Validation
target1:0:4: FAST-160 WIDE SCSI 320.0 MB/s DT IU RTI PCOMP (6.25 ns, offset 64)
st 1:0:4:0: Attached scsi tape st0
st 1:0:4:0: st0: try direct i/o: yes (alignment 512 B)
st 1:0:4:0: Attached scsi generic sg2 type 1
scsi 1:0:4:1: Medium Changer HP MSL G3 Series 3.40 PQ: 0 ANSI: 5
ch0: type #1 (mt): 0x0+1 [medium transport]
ch0: type #2 (st): 0x3e9+24 [storage]
ch0: type #3 (ie): 0x0+0 [import/export]
ch0: type #4 (dt): 0x1+1 [data transfer]
ch0: dt 0x1: ID 4, LUN 0, name: HP Ultrium 4-SCSI B23W
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 1:0:4:1: Attached scsi changer ch0
ch 1:0:4:1: Attached scsi generic sg3 type 8
Fusion MPT misc device (ioctl) driver 3.04.05
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
All tests, that are mentioned at TapeTestingChapter were passed without any error. Here is the msl2024 compatibility test log.
The only problem is the promised encryption with AES 256 bit. It seems, that you can only enable it using a backup-software, that can issue that kind of SCSI-commands, what bacula actually unfortunately can't do. After asking for a kind of documentation for this functionality, i got following answer from a HP-support in UK:
My question was literally: how do i enable hardware encryption on my LTO4 Ultrium 1840 drive inside the msl2024?
At first i got this very common answer from a first-level-support:
Wie telefonisch besprochen, schicke ich Ihnen die
Information von Level 2:
--- Begin forwarded message ---
andrew wrote:
LTO 4 data encryption technique.
Encryption is fairly straight forward and is only
applicable for LTO4 technology
Set the key in the drive and then use it. You need the
application to set the key for both the writing and then
the reading The important bit is remembering the key if you want
encryption otherwise it is too late. Key setting is a SCSI
command. The customer cannot set anything manually
on the drive etc its all done through software. If you set
the key and write, you'll have an encrypted tape. LTO4
only You need the key set again in order to read the data
on the encrypted tape again.
If you don't set the key during the read cycle then the drive
will return an error and will not be able to read the tape.
Two ways to set the key:
1) Use the ISV (independent software vender) application -
which must support it. Customer needs to check with their
ISV whether they support this functionality or not and they
should get instructions from them as to how to use it.
2) Use an independent key management appliance
which is only applicable to libraries but unfortunately
this software is still being developed at the moment
and is not available yet to our customers.
regards andrew
--- end forwarded message ---
With regards
1st Level Support
After then, i asked for the direct email of "andrew" and wrote him directly:
if you don't mind, i decided to try to contact You directly, instead
of to write to the first-level-support.
My question is following: how can i activate encryption in my
LTO-4-drive on my own.
I mean, You can't serious advice to "Use the ISV (independent
software vendor) application"; there are only *5* vendors
(according to the HP-EBS-Matrix, see attachment), that
support this option.
And i.e. i use none of these products.
I mean it must be a single command that is submitted to the
drive via SCSI-interface to set a 256-bit-long string as a key,
not more. And the encryption logic etc. is done by the
tapedrive-chip.
Please give me at least a small hint or "direction to dig" ,
where can i get further info about setting a key manually.
Maybe a link to kind a "LTO-4-SCSI-CRYPTO-API" (? if there
is a such thing?)
Thank you in advance!
Answer from Andrew
I am afraid I could not do this as it would not be supported
by HP. Afraid my hands are tied on this one Vladimir.
I will keep an eye out for the encryption software and let
you know when it is released. Unfortunately there is no
release date set yet.
Regards
andrew
and the closing email from HP:
Closing statement from HP:
Currently there are only a few supported backup software
applications which are supported by HP using the LTO
encryption method (these can be found on the hp.com web
site for your
specific product.) All other support of ISV software using encryption
has to wait until HP releases the software encryption key
which will put the LTO4 drive into encryption mode.
There is no official release date for this software, we
have to wait for our division to relay a release date.
We are not able to provide more information about LTO4 encryption.
With regards
That's it...
If you need the configuration-files or any questions to my config, feel free to mail me or leave a comment.
Greetings
Vladimirs Vecgailis
Update @ 16.10.2008: i am often asked to send the configuration files; i'll better put them for download here:
openvms C example...
Search the HP ITRC site for some example code I've written in C to set the LTO4 key. It has been working fine so far... Seach for "lto4 encryption" and you should find it.
msl2024 config?
First, thanks so much for sharing your bacula configs! They have been a tremendous help.
Second, will you share how you have the changer configured in the MSL2024 for this? I have set mine to run sequentially, and have identified it in my OS, but, bacula seems to not be able to communicate with that changer as yet.
I can run an mtx inquire against it, and get correct information, but, status, etc. are failing, and I think it is partially due to that sequential vs. random setting.
Thanks again!
you're right,
that's the point - the program is written for openVMS... :-)
If you could kindly modify it so it runs on x86 @ kernel 2.6 ...
Hopey
Thanks for sharing the config files. They were much help for me setting my bacup config.
Hopey
you are welcome :-)
you are welcome :-)
Kommentar hinzufügen