HP LTO 4 FC, LTO 4 SCSI, LTO 4 SAS instruction

Image 81

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

Contents

LTO 4 FC, SCSI and SAS drives volume 2 software integrationHP LTO Ultrium tape drives technical reference manual HP restricted Legal and notice information 1 Designing backup applications Contents2 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 documentsDocuments specific to HP Ultrium drives Drives-general Operation Installation and configurationCartridges Interface Dealing with errors Maintenance and troubleshooting General documents and standardization LTO Ultrium features Non-immediate commands 1 Designing backup applicationsOptimizing performance Large data transfer size Managing the use of tapes Cleaning tape headsInformation in Cartridge Memory Monitoring tape use Diagnostic logs Design goals for LTO backup applicationsTapeAlert Displaying drive information Include the capability to download firmware 2 Configuration and initialization Inquiry string recoveryOperating system drivers Example 16 Configuration and initializationSCSI protocol, regardless of transport or interface type Support for additional LUN Enabling additional LUN supportSupporting additional LUNs 18 Configuration and initialization Using MODE SENSE Using Cartridge Memory attributes3 Use of tapes LTO cartridge memory Tape status and capacity Finding the remaining capacityInterpreting Log Sense data Using the SET CAPACITY command Command descriptor blockCDB fields WORM media Changes to SCSI commandsHow WORM media works New additional sense codes and TapeAlert flags ERASE commands rejected Error Usage pageSET CAPACITY command Re-writing media labels Using CM to check tape integrity Behavior with a missing or inconsistent EOD valueUnique media identifier Responding to Cartridge Memory data Load countBarcode support Corrective action RWW retry counts Ways of optimizing performance 4 Factors affecting performanceDetecting the drive’s speed Ensuring the recommended minimum transfer sizes Using the Performance Log page for diagnosing problems Using Cartridge Memory instead of tape headersTime-out values Media type identification Recommended support of log pages Factors affecting performanceHost-related factors Recommendation Examplewhere 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 featuresAutomation interface Further information Automation/Device Interface ADI Automation Control Interface ACI Modes of usage through ACISlave to a library controller ACI command set ACI commands that affect drive streaming performanceSCSI pass-through mode Backward compatibility New features in ACI SCSI command Encryption support Supporting the ACI protocol Further detailsRecommended 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 tapeACI protocol communications retry Upgrading the drive firmware Firmware upgrade via ACI Firmware upgrade via the primary host interfaceLibrary firmware upgrade via tape Handling irregular cartridges Expired cleaning cartridge HP-configured or Universal Cleaning cartridge HP-configured or UniversalNon-HP Ultrium 1 cleaning cartridge Unreadable data cartridge Data cartridge with unreadable CM Valid firmware upgrade cartridgeCartridge fails to seat or load Cartridge cannot be loaded Cleaning Frequently asked questionsInvalid firmware upgrade cartridge Is there separate firmware for drives intended to go into libraries? Resetting drives Backup softwareResetting via the ACI Reset command Resetting using the ACIRSTL line Controlling data compression Accessing Cartridge Memory without threading the tapeOther mode page information Buffer size at EW-EOM Write delay time Rewind on resetPartition size 52 Supporting Ultrium features Sense keys-actions to take 6 Sense keys and codesAction Console Message For additional sense codes, see “3h-MEDIUM ERROR” on “3h-MEDIUM ERROR” on page 62 . Also see the Media Accesslog the error, terminate I/O to the drive, and pass the appropriate error to the calling application Console Message ActionAction Console Message Action Physical Additional sense codes-actions to takeEnd-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 accessThe command cannot be executed because the specified 60 Sense keys and codes mechanism tests are being executed. When the tests are 3h-MEDIUM ERROR A READ , SPACE , WRITE or WRITE FILEMARKS command62 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 5h-ILLEGAL REQUEST A MODE SELECT parameter list sent to the drive contains68 Sense keys and codes persistent reservation using the PERSISTENT RESERVE OUT 6h-UNIT ATTENTIONallowed 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 persistentWRITE BUFFER or MAINTENANCE OUT command A SET DEVICE IDENTIFIER command has been successful 7h-DATA PROTECTION Action 8h-BLANK CHECK Bh-ABORTED COMMAND READ BUFFER commandrelated to a missing EOD data set. The most likely cause Dh-VOLUME OVERFLOW A WRITE or WRITE FILEMARKS command has encountered76 Sense keys and codes 1. Retrieve fault information Typical escalation procedure3. Allow the user to try recovery 4. Allow the user to reset devices Supporting TapeAlert Monitoring the condition of the drive and media Type FlagsPage Page Page Page Page Page Page TapeAlert models Designing software to use the TapeAlert log Reading the TapeAlert log TapeAlert polling usage modelTapeAlert informational exception usage model One-Button Disaster Recovery OBDR Responding to the ‘Clean’ LEDSupporting OBDR Requirements for drivers and logical device managers Providing pass-through mode Glossary see ”read-while-write” Index Page Page HP restricted