HP LTO 4 SCSI, LTO 4 FC, LTO 4 SAS manual Glossary

Page 91
Glossary

Glossary

ANSI

American National Standards Institute, which sets standards for, amongst other things,

 

SCSI and the safety of electrical devices.

BOM

Beginning Of Media. The first point on the tape that can be accessed by the drive.

buffered mode

A mode of data transfer in write operations that facilitates tape streaming. It is selected

 

by setting the Buffered Mode Field to 1 or 2 in the SCSI MODE SELECT Parameter List

 

header.

compression

A procedure in which data is transformed by the removal of redundant information in

 

order to reduce the number of bits required to represent the data.

compression ratio

A measure of how much compression has occurred, defined as the ratio of the amount

 

of uncompressed data to the amount of compressed data into which it is transformed.

 

The LTO-DC algorithm can typically achieve a compression ratio of between 2:1 and

 

4:1 depending on the nature of the data.

decompression

A procedure in which the original data is generated from compressed data.

ECMA

European Computer Manufacturers Association. The European equivalent of ANSI.

EOD

End Of Data. An area that signifies the end of the valid data. If new data is written

 

over a larger quantity of old data, it is possible for data to exist after EOD, but

 

because it is after EOD, this old data is no longer valid.

EOM

End Of Media format. The last usable point on the tape.

EW-EOM

Early Warning End Of Media. A physical mark or a device-computed position on the

 

tape that tells the drive that it is approaching EOM.

filemark

A mark written by the host. It does not necessarily separate files; it is up to the host to

 

assign a meaning to the mark.

FRU

Field Replaceable Unit, an assembly or group of components that is replaced in its

 

entirety by Service Engineers when it contains a fault.

hard error

An uncorrectable data error.

host

The host computer system acting as controller for the drive.

load

The process in which the drive takes in an inserted cartridge and goes online.

LUN

Logical Unit Number, by which different devices at a particular SCSI ID can be

 

addressed individually. The drive has a fixed LUN of 0.

HP LTO Ultrium 4 drives technical reference manual, volume 2: software integration 91 HP restricted

Image 91
Contents HP restricted volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP LTO Ultrium tape drives technical reference manualLegal and notice information 3 Use of tapes Contents1 Designing backup applications 2 Configuration and initialization4 Factors affecting performance 5 Supporting Ultrium features7 Exception handling 6 Sense keys and codesHP restricted Drives-general Related documentsDocumentation map Documents specific to HP Ultrium drivesInterface Installation and configurationOperation CartridgesDealing with errors Maintenance and troubleshootingGeneral documents and standardization LTO Ultrium featuresLarge data transfer size 1 Designing backup applicationsNon-immediate commands Optimizing performanceMonitoring tape use Cleaning tape headsManaging the use of tapes Information in Cartridge MemoryDisplaying drive information Design goals for LTO backup applicationsDiagnostic logs TapeAlertInclude the capability to download firmware Inquiry string recovery 2 Configuration and initializationOperating system drivers 16 Configuration and initialization ExampleSCSI protocol, regardless of transport or interface type Enabling additional LUN support Support for additional LUNSupporting additional LUNs 18 Configuration and initialization LTO cartridge memory Using Cartridge Memory attributesUsing MODE SENSE 3 Use of tapesFinding the remaining capacity Tape status and capacityInterpreting Log Sense data Command descriptor block Using the SET CAPACITY commandCDB fields New additional sense codes and TapeAlert flags Changes to SCSI commandsWORM media How WORM media worksRe-writing media labels Error Usage pageERASE commands rejected SET CAPACITY commandBehavior with a missing or inconsistent EOD value Using CM to check tape integrityUnique media identifier Load count Responding to Cartridge Memory dataBarcode support Corrective action RWW retry countsEnsuring the recommended minimum transfer sizes 4 Factors affecting performanceWays of optimizing performance Detecting the drive’s speedMedia type identification Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Time-out valuesFactors affecting performance Recommended support of log pagesHost-related factors makes sense to split heavily used FC cards across separate PCI busses ExampleRecommendation where possible or a reasonably sized RAID system. More disks meansDo not interleave write commands with other commands, such as READ Drive-related factorsFormat-related factors Page 34 Factors affecting performance Further information 5 Supporting Ultrium featuresCartridge Memory LTO-CM Automation interfaceAutomation/Device Interface ADI Modes of usage through ACI Automation Control Interface ACISlave to a library controller ACI commands that affect drive streaming performance ACI command setSCSI pass-through mode Backward compatibility New features in ACISCSI command Encryption support 42 Supporting Ultrium features Further detailsSupporting the ACI protocol Recommended ACI time-out valuesTreatment of reserved fields Recommended power-up sequenceRecommended load-unload configuration Upgrading the drive firmware Firmware upgrade via tapeRecommended Get Drive Status polling frequency ACI protocol communications retryHandling irregular cartridges Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Library firmware upgrade via tapeUnreadable data cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Non-HP Ultrium 1 cleaning cartridgeCartridge cannot be loaded Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge fails to seat or loadIs there separate firmware for drives intended to go into libraries? Frequently asked questionsCleaning Invalid firmware upgrade cartridgeResetting using the ACIRSTL line Backup softwareResetting drives Resetting via the ACI Reset commandBuffer size at EW-EOM Accessing Cartridge Memory without threading the tapeControlling data compression Other mode page information52 Supporting Ultrium features Rewind on resetWrite delay time Partition sizeConsole Message 6 Sense keys and codesSense keys-actions to take Actionerror to the calling application “3h-MEDIUM ERROR” on page 62 . Also see the Media AccessFor additional sense codes, see “3h-MEDIUM ERROR” on log the error, terminate I/O to the drive, and pass the appropriateConsole Message ActionConsole Message Actionpage reached, unable to fit Additional sense codes-actions to takePhysical End-of-Tape0h-NO SENSE 2h-NOT READY 1h-RECOVERED ERROR60 Sense keys and codes The software must issue a LOAD before media accessLUN not accessible, port in The command cannot be executed because the specifiedmechanism tests are being executed. When the tests are A READ , SPACE , WRITE or WRITE FILEMARKS command 3h-MEDIUM ERROR62 Sense keys and codes and the drive. Based on this, ask the user to clean the Send a console message that an unrecovered error on64 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, REWIND4h-HW ERROR A MODE SELECT parameter list sent to the drive contains 5h-ILLEGAL REQUEST68 Sense keys and codes 32 initiators to register, using PERSISTENT RESERVE OUT 6h-UNIT ATTENTIONpersistent reservation using the PERSISTENT RESERVE OUT allowed to execute. In other words, some commands canAction A SET DEVICE IDENTIFIER command has been successful service action removed all reservations and the persistentA PERSISTENT RESERVE OUT command was executed WRITE BUFFER or MAINTENANCE OUT command7h-DATA PROTECTION Action 8h-BLANK CHECK READ BUFFER command Bh-ABORTED COMMANDrelated to a missing EOD data set. The most likely cause A WRITE or WRITE FILEMARKS command has encountered Dh-VOLUME OVERFLOW76 Sense keys and codes 4. Allow the user to reset devices Typical escalation procedure1. Retrieve fault information 3. Allow the user to try recoverySupporting TapeAlert Monitoring the condition of the drive and mediaType FlagsPage Page Page Page Page Page Page TapeAlert models Designing software to use the TapeAlert logTapeAlert polling usage model Reading the TapeAlert logTapeAlert informational exception usage model Responding to the ‘Clean’ LED One-Button Disaster Recovery OBDRSupporting OBDR Requirements for drivers and logical device managers Providing pass-through modeGlossary see ”read-while-write” Index Page Page HP restricted