What's new in l&tt 4.14 – HP StoreEver TapeAssure Software User Manual
Page 12
◦
Added the LTO Data Assessment Test, which is aimed at checking the quality of the data
on tape. (L&TT 4.14 SR2)
◦
LTO support ticket device analysis rules now lists all the polling hosts it can detect rather
than just the first one. (L&TT 4.14 SR1)
◦
LTO support ticket and Drive Assessment Test now includes off-track margin assessment.
(L&TT 4.14 SR1)
◦
Stronger messaging to update LTO firmware to encourage adoption of significant reliability
improvements to the drive. (L&TT 4.14 SR1)
•
Virtual libraries and D2D backup devices — Added support for D2D virtual LTO-5 drives and
ESL-e libraries in L&TT 4.14 SR1
•
Other backup devices — Same as L&TT 4.14
•
Operating system specific
Red Hat EL 6.3 support added.
◦
◦
SuSE 10 SP2 support added.
◦
Mac OSX 10.8 support added.
◦
Mac OSX 10.7 support added (L&TT 4.14 SR1)
◦
Fixed a case with Windows Vista and Windows 7 where APPCRASH appeared on exit.
(L&TT 4.14 SR1)
◦
Fixed a case when the HP-UX Agile driver appeared unresponsive after a scan finds too
many devices. (L&TT 4.14 SR1)
•
Generic to tool — Implemented improved error decoding throughout the tool. (L&TT 4.14 SR1)
What's new in L&TT 4.14
L&TT 4.14 targets:
•
New Ethernet access mode for LTO-5 automation drives.
•
Increased sensitivity of LTO read margin calculations.
•
Removed StorageWorks branding, resulting in a new install location.
Enhancements and fixes in L&TT 4.14
•
Tape libraries and autoloaders
LTO 5 automation drives can now be accessed via Ethernet, enabling tickets to be pulled
and tests to be run without the need to install L&TT on the host server. (See
◦
HP library LTO-5 and LTO-6 drives over Ethernet” (page 82)
.) Please be aware of one
known issue that selecting a drive in an ESL-e selection takes 3 minutes. The other library
types select within around 20 seconds. The drives need the very latest LTO-5 firmware to
support this feature.
◦
The 1/8 G2 Tape Autoloader and MSL library front panel error messages now match
wording of the support ticket more closely.
12
Introduction