How WORM media works, Changes to SCSI commands | HP LTO 4 SCSI

Image 22

HP LTO 4 SCSI, LTO 4 FC How WORM media works, Changes to SCSI commands, New additional sense codes and TapeAlert flags

Contents

HP LTO Ultrium tape drives technical reference manual volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP restricted Legal and notice information 2 Configuration and initialization Contents1 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 documentsDocumentation map Drives-general Cartridges Installation and configurationOperation Interface Maintenance and troubleshooting Dealing with errors LTO Ultrium features General documents and standardization Optimizing performance 1 Designing backup applicationsNon-immediate commands Large data transfer size Information in Cartridge Memory Cleaning tape headsManaging the use of tapes Monitoring tape use TapeAlert Design goals for LTO backup applicationsDiagnostic logs Displaying drive information Include 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 3 Use of tapes Using Cartridge Memory attributesUsing MODE SENSE LTO cartridge memory Finding the remaining capacity Tape status and capacityInterpreting Log Sense data Command descriptor block Using the SET CAPACITY commandCDB fields How WORM media works Changes to SCSI commandsWORM media New additional sense codes and TapeAlert flags SET CAPACITY command Error Usage pageERASE commands rejected Re-writing media labels Behavior with a missing or inconsistent EOD value Using CM to check tape integrityUnique media identifier Load count Responding to Cartridge Memory dataBarcode support RWW retry counts Corrective action Detecting the drive’s speed 4 Factors affecting performanceWays of optimizing performance Ensuring the recommended minimum transfer sizes Time-out values Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Media type identification Factors affecting performance Recommended support of log pagesHost-related factors where possible or a reasonably sized RAID system. More disks means ExampleRecommendation 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 featuresCartridge Memory LTO-CM Further information Automation/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 New features in ACI Backward compatibility SCSI command Encryption support Recommended ACI time-out values Further detailsSupporting 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 tapeRecommended Get Drive Status polling frequency Upgrading the drive firmware Library firmware upgrade via tape Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Handling irregular cartridges Non-HP Ultrium 1 cleaning cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Unreadable data cartridge Cartridge fails to seat or load Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge cannot be loaded Invalid firmware upgrade cartridge Frequently asked questionsCleaning Is there separate firmware for drives intended to go into libraries? Resetting via the ACI Reset command Backup softwareResetting drives Resetting using the ACIRSTL line Other mode page information Accessing Cartridge Memory without threading the tapeControlling data compression Buffer size at EW-EOM Partition size Rewind on resetWrite delay time 52 Supporting Ultrium features Action 6 Sense keys and codesSense 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 AccessFor additional sense codes, see “3h-MEDIUM ERROR” on error to the calling application Action ActionConsole Message Console Message Console Message End-of-Tape Additional sense codes-actions to takePhysical 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 accessLUN 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 ERROR62 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 REQUEST68 Sense keys and codes allowed to execute. In other words, some commands can 6h-UNIT ATTENTIONpersistent 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 persistentA 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 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 3. Allow the user to try recovery Typical escalation procedure1. Retrieve fault information 4. Allow the user to reset devices Monitoring the condition of the drive and media Supporting TapeAlert Flags TypePage Page Page Page Page Page Page Designing software to use the TapeAlert log TapeAlert models TapeAlert polling usage model Reading the TapeAlert logTapeAlert informational exception usage model Responding to the ‘Clean’ LED One-Button Disaster Recovery OBDRSupporting OBDR Providing pass-through mode Requirements for drivers and logical device managers Glossary see ”read-while-write” Index Page Page HP restricted