Page 22
The following table gives the minimum acceptable Capacity Proportion Values and the approximate capacity they will give:
Cartridge | Min. capacity proportion value | Resultant approx. min. capacity | Max. capacity |
Ultrium 2 | 1605h | 17.2 GB | 200 GB |
Ultrium 3 | 151Ah | 33 GB | 400 GB |
Ultrium 4 | 1055h | 51 GB | 800 GB |
NOTE: Capacities are approximate and can be affected by defects that reduce the actual capacity of the tape. Other factors, such as compression and block packing, may also affect capacity.
WORM media
HP Ultrium-3 WORM (Write Once—Read Many) data cartridges are two-tone grey/yellow to distinguish them from RW media. They have a unique Cartridge Type stored in the Cartridge Memory, so that they will be rejected by non-WORM compatible drives. For automation configurations with auto-eject disabled, the cartridge will not be physically ejected from the drive but held at the “ready eject” position.
The write-protection tab behaves as on Read/Write (RW) cartridges.
How WORM media works
Drives use the EOPD (End of Protected Data) value to control the use of WORM tapes.
EOPD is a logical position on tape that is automatically calculated based on the End of Data (EOD) value read from the Cartridge Memory (CM) when the cartridge is loaded into the drive. The EOD value is an “intrinsic” code stored and protected in the Cartridge Memory of each WORM cartridge, and updated after each write session. The EOPD indicates that data between BOM and this position cannot be overwritten.
The EOPD value is held within the drive’s memory. It is updated automatically and continuously as each block of data (typically 64 or 128 KB) is written to tape, so the EOPD value indicates a logical position immediately after the last block of data written to tape.
When the cartridge is unloaded, the drive updates the EOD value in CM to reflect the end of successfully written data on the cartridge, and clears the EOPD value stored within the drive. Any future writes to the cartridge will occur after the location of the EOD, which will become the initial location for EOPD during the next write operation.
Changes to SCSI commands
New additional sense codes and TapeAlert flags
ASC/Qs:
•300Ch (WORM medium—overwrite attempted)
•300Dh (WORM Medium—integrity check failed)
22 Use of tapes
HP restricted
Contents
HP LTO Ultrium tape drives technical reference manual
volume 2 software integration
LTO 4 FC, SCSI and SAS drives
HP restricted
Legal and notice information
2 Configuration and initialization
Contents
1 Designing backup applications
3 Use of tapes
5 Supporting Ultrium features
4 Factors affecting performance
6 Sense keys and codes
7 Exception handling
HP restricted
Documents specific to HP Ultrium drives
Related documents
Documentation map
Drives-general
Cartridges
Installation and configuration
Operation
Interface
Maintenance and troubleshooting
Dealing with errors
LTO Ultrium features
General documents and standardization
Optimizing performance
1 Designing backup applications
Non-immediate commands
Large data transfer size
Information in Cartridge Memory
Cleaning tape heads
Managing the use of tapes
Monitoring tape use
TapeAlert
Design goals for LTO backup applications
Diagnostic logs
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
3 Use of tapes
Using Cartridge Memory attributes
Using MODE SENSE
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
How WORM media works
Changes to SCSI commands
WORM media
New additional sense codes and TapeAlert flags
SET CAPACITY command
Error Usage page
ERASE commands rejected
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
RWW retry counts
Corrective action
Detecting the drive’s speed
4 Factors affecting performance
Ways of optimizing performance
Ensuring the recommended minimum transfer sizes
Time-out values
Using Cartridge Memory instead of tape headers
Using the Performance Log page for diagnosing problems
Media type identification
Factors affecting performance
Recommended support of log pages
Host-related factors
where possible or a reasonably sized RAID system. More disks means
Example
Recommendation
makes sense to split heavily used FC cards across separate PCI busses
Drive-related factors
Do not interleave write commands with other commands, such as READ
Format-related factors
Page
34 Factors affecting performance
Automation interface
5 Supporting Ultrium features
Cartridge Memory LTO-CM
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
New features in ACI
Backward compatibility
SCSI command
Encryption support
Recommended ACI time-out values
Further details
Supporting the ACI protocol
42 Supporting Ultrium features
Recommended power-up sequence
Treatment of reserved fields
Recommended load-unload configuration
ACI protocol communications retry
Firmware upgrade via tape
Recommended Get Drive Status polling frequency
Upgrading the drive firmware
Library firmware upgrade via tape
Firmware upgrade via the primary host interface
Firmware upgrade via ACI
Handling irregular cartridges
Non-HP Ultrium 1 cleaning cartridge
Cleaning cartridge HP-configured or Universal
Expired cleaning cartridge HP-configured or Universal
Unreadable data cartridge
Cartridge fails to seat or load
Valid firmware upgrade cartridge
Data cartridge with unreadable CM
Cartridge cannot be loaded
Invalid firmware upgrade cartridge
Frequently asked questions
Cleaning
Is there separate firmware for drives intended to go into libraries?
Resetting via the ACI Reset command
Backup software
Resetting drives
Resetting using the ACIRSTL line
Other mode page information
Accessing Cartridge Memory without threading the tape
Controlling data compression
Buffer size at EW-EOM
Partition size
Rewind on reset
Write delay time
52 Supporting Ultrium features
Action
6 Sense keys and codes
Sense keys-actions to take
Console Message
log the error, terminate I/O to the drive, and pass the appropriate
“3h-MEDIUM ERROR” on page 62 . Also see the Media Access
For additional sense codes, see “3h-MEDIUM ERROR” on
error to the calling application
Action
Action
Console Message
Console Message
Console Message
End-of-Tape
Additional sense codes-actions to take
Physical
reached, unable to fit
0h-NO SENSE
1h-RECOVERED ERROR
2h-NOT READY
The command cannot be executed because the specified
The software must issue a LOAD before media access
LUN not accessible, port in
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
Send a console message that an unrecovered error on
and the drive. Based on this, ask the user to clean the
64 Sense keys and codes
Send a message to the console indicating that there is
The current command such as READ, SPACE, REWIND
66 Sense keys and codes
4h-HW ERROR
A MODE SELECT parameter list sent to the drive contains
5h-ILLEGAL REQUEST
68 Sense keys and codes
allowed to execute. In other words, some commands can
6h-UNIT ATTENTION
persistent reservation using the PERSISTENT RESERVE OUT
32 initiators to register, using PERSISTENT RESERVE OUT
Action
WRITE BUFFER or MAINTENANCE OUT command
service action removed all reservations and the persistent
A PERSISTENT RESERVE OUT command was executed
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
3. Allow the user to try recovery
Typical escalation procedure
1. Retrieve fault information
4. Allow the user to reset devices
Monitoring the condition of the drive and media
Supporting TapeAlert
Flags
Type
Page
Page
Page
Page
Page
Page
Page
Designing software to use the TapeAlert log
TapeAlert models
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
Providing pass-through mode
Requirements for drivers and logical device managers
Glossary
see ”read-while-write”
Index
Page
Page
HP restricted