LTO 4 FC, SCSI and SAS drives
volume 2 software integration
HP LTO Ultrium tape drives technical reference manual
HP restricted
Legal and notice information
1 Designing backup applications
Contents
2 Configuration and initialization
3 Use of tapes
4 Factors affecting performance
5 Supporting Ultrium features
7 Exception handling
6 Sense keys and codes
HP restricted
Documentation map
Related documents
Documents specific to HP Ultrium drives
Drives-general
Operation
Installation and configuration
Cartridges
Interface
Dealing with errors
Maintenance and troubleshooting
General documents and standardization
LTO Ultrium features
Non-immediate commands
1 Designing backup applications
Optimizing performance
Large data transfer size
Managing the use of tapes
Cleaning tape heads
Information in Cartridge Memory
Monitoring tape use
Diagnostic logs
Design goals for LTO backup applications
TapeAlert
Displaying drive information
Include the capability to download firmware
Inquiry string recovery
2 Configuration and initialization
Operating system drivers
16 Configuration and initialization
Example
SCSI protocol, regardless of transport or interface type
Enabling additional LUN support
Support for additional LUN
Supporting additional LUNs
18 Configuration and initialization
Using MODE SENSE
Using Cartridge Memory attributes
3 Use of tapes
LTO cartridge memory
Finding the remaining capacity
Tape status and capacity
Interpreting Log Sense data
Command descriptor block
Using the SET CAPACITY command
CDB fields
WORM media
Changes to SCSI commands
How WORM media works
New additional sense codes and TapeAlert flags
ERASE commands rejected
Error Usage page
SET CAPACITY command
Re-writing media labels
Behavior with a missing or inconsistent EOD value
Using CM to check tape integrity
Unique media identifier
Load count
Responding to Cartridge Memory data
Barcode support
Corrective action
RWW retry counts
Ways of optimizing performance
4 Factors affecting performance
Detecting the drive’s speed
Ensuring the recommended minimum transfer sizes
Using the Performance Log page for diagnosing problems
Using Cartridge Memory instead of tape headers
Time-out values
Media type identification
Factors affecting performance
Recommended support of log pages
Host-related factors
Recommendation
Example
where possible or a reasonably sized RAID system. More disks means
makes sense to split heavily used FC cards across separate PCI busses
Do not interleave write commands with other commands, such as READ
Drive-related factors
Format-related factors
Page
34 Factors affecting performance
Cartridge Memory LTO-CM
5 Supporting Ultrium features
Automation interface
Further information
Automation/Device Interface ADI
Modes of usage through ACI
Automation Control Interface ACI
Slave to a library controller
ACI commands that affect drive streaming performance
ACI command set
SCSI pass-through mode
Backward compatibility
New features in ACI
SCSI command
Encryption support
Supporting the ACI protocol
Further details
Recommended ACI time-out values
42 Supporting Ultrium features
Treatment of reserved fields
Recommended power-up sequence
Recommended load-unload configuration
Recommended Get Drive Status polling frequency
Firmware upgrade via tape
ACI protocol communications retry
Upgrading the drive firmware
Firmware upgrade via ACI
Firmware upgrade via the primary host interface
Library firmware upgrade via tape
Handling irregular cartridges
Expired cleaning cartridge HP-configured or Universal
Cleaning cartridge HP-configured or Universal
Non-HP Ultrium 1 cleaning cartridge
Unreadable data cartridge
Data cartridge with unreadable CM
Valid firmware upgrade cartridge
Cartridge fails to seat or load
Cartridge cannot be loaded
Cleaning
Frequently asked questions
Invalid firmware upgrade cartridge
Is there separate firmware for drives intended to go into libraries?
Resetting drives
Backup software
Resetting via the ACI Reset command
Resetting using the ACIRSTL line
Controlling data compression
Accessing Cartridge Memory without threading the tape
Other mode page information
Buffer size at EW-EOM
Write delay time
Rewind on reset
Partition size
52 Supporting Ultrium features
Sense keys-actions to take
6 Sense keys and codes
Action
Console Message
For additional sense codes, see “3h-MEDIUM ERROR” on
“3h-MEDIUM ERROR” on page 62 . Also see the Media Access
log the error, terminate I/O to the drive, and pass the appropriate
error to the calling application
Console Message
Action
Action
Console Message
Action
Physical
Additional sense codes-actions to take
End-of-Tape
reached, unable to fit
0h-NO SENSE
2h-NOT READY
1h-RECOVERED ERROR
LUN not accessible, port in
The software must issue a LOAD before media access
The command cannot be executed because the specified
60 Sense keys and codes
mechanism tests are being executed. When the tests are
A READ , SPACE , WRITE or WRITE FILEMARKS command
3h-MEDIUM ERROR
62 Sense keys and codes
and the drive. Based on this, ask the user to clean the
Send a console message that an unrecovered error on
64 Sense keys and codes
Send a message to the console indicating that there is
66 Sense keys and codes
The current command such as READ, SPACE, REWIND
4h-HW ERROR
A MODE SELECT parameter list sent to the drive contains
5h-ILLEGAL REQUEST
68 Sense keys and codes
persistent reservation using the PERSISTENT RESERVE OUT
6h-UNIT ATTENTION
allowed to execute. In other words, some commands can
32 initiators to register, using PERSISTENT RESERVE OUT
Action
A PERSISTENT RESERVE OUT command was executed
service action removed all reservations and the persistent
WRITE BUFFER or MAINTENANCE OUT command
A SET DEVICE IDENTIFIER command has been successful
7h-DATA PROTECTION
Action
8h-BLANK CHECK
READ BUFFER command
Bh-ABORTED COMMAND
related to a missing EOD data set. The most likely cause
A WRITE or WRITE FILEMARKS command has encountered
Dh-VOLUME OVERFLOW
76 Sense keys and codes
1. Retrieve fault information
Typical escalation procedure
3. Allow the user to try recovery
4. Allow the user to reset devices
Supporting TapeAlert
Monitoring the condition of the drive and media
Type
Flags
Page
Page
Page
Page
Page
Page
Page
TapeAlert models
Designing software to use the TapeAlert log
TapeAlert polling usage model
Reading the TapeAlert log
TapeAlert informational exception usage model
Responding to the ‘Clean’ LED
One-Button Disaster Recovery OBDR
Supporting OBDR
Requirements for drivers and logical device managers
Providing pass-through mode
Glossary
see ”read-while-write”
Index
Page
Page
HP restricted