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