HP LTO 4 SCSI Design goals for LTO backup applications, TapeAlert, Diagnostic logs, Drive tests

Page 13

See “Tape Capacity Log Page” under the LOG SENSE command in Chapter 3 of The SCSI Interface, Volume 3 of the HP LTO Ultrium Technical Reference Manual for more information.

While the reliability of tape products and applications is getting better all the time, problems do still occur. There are some very simple techniques that could be incorporated by application developers to simplify the process that a user must go through to resolve problems.

For additional information, see “Exception handling” on page 77.

TapeAlert

The TapeAlert facility in HP Ultrium drives allows applications to help avoid trouble by prompting the user to take remedial action, or in some cases, through the application automatically performing remedial actions itself.

For example, if the drive is experiencing trouble writing, the software can prompt the user to clean the heads, or, if there are several drives or an autoloader, automatically clean the heads without involving the user.

See “Monitoring the condition of the drive and media” on page 78 for more details.

Diagnostic logs

SCSI tape drives report problems in response to a REQUEST SENSE command from the host. If the backup application stores this information in a log file, it becomes significantly easier to troubleshoot problems, because the data can be used to pinpoint what is wrong.

Displaying drive information

Troubleshooting can also be simplified by giving users the ability to look at the drive’s firmware revision, and information about the host bus adapter. This information can be found by executing an INQUIRY command, and can then be displayed, or stored in a log file.

Drive tests

A basic read/write test should be included in a backup application to check the integrity of the hardware. This should also allow the user to scan the SCSI bus and to solve problems concerning the device setup and configuration.

Design goals for LTO backup applications

Use large SCSI read/write transfer sizes (256 KB is recommended).

Incorporate data compression control and report the compression ratios achieved.

Consider where to store directory information depending on the nature of the application.

Only use immediate WRITE FILEMARK commands, but avoid using other commands in immediate mode.

Use Cartridge Memory information to measure tape quality before backing up starts.

Use the TapeAlert log to prompt the user to take remedial action to avoid problems.

Use “cleaning required” indicators in the software to either prompt the user or enable the library to use a cleaning cartridge to clean the drive heads.

Allow users to set custom cleaning schedules.

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

Image 13
Contents LTO 4 FC, SCSI and SAS drives volume 2 software integrationHP LTO Ultrium tape drives technical reference manual HP restrictedLegal and notice information 1 Designing backup applications Contents2 Configuration and initialization 3 Use of tapes4 Factors affecting performance 5 Supporting Ultrium features7 Exception handling 6 Sense keys and codesHP restricted Documentation map Related documentsDocuments specific to HP Ultrium drives Drives-generalOperation Installation and configurationCartridges InterfaceDealing with errors Maintenance and troubleshootingGeneral documents and standardization LTO Ultrium featuresNon-immediate commands 1 Designing backup applicationsOptimizing performance Large data transfer sizeManaging the use of tapes Cleaning tape headsInformation in Cartridge Memory Monitoring tape useDiagnostic logs Design goals for LTO backup applicationsTapeAlert Displaying drive informationInclude 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 Using MODE SENSE Using Cartridge Memory attributes3 Use of tapes LTO cartridge memoryFinding the remaining capacity Tape status and capacityInterpreting Log Sense data Command descriptor block Using the SET CAPACITY commandCDB fields WORM media Changes to SCSI commandsHow WORM media works New additional sense codes and TapeAlert flagsERASE commands rejected Error Usage pageSET CAPACITY command Re-writing media labelsBehavior 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 countsWays of optimizing performance 4 Factors affecting performanceDetecting the drive’s speed Ensuring the recommended minimum transfer sizesUsing the Performance Log page for diagnosing problems Using Cartridge Memory instead of tape headersTime-out values Media type identificationFactors affecting performance Recommended support of log pagesHost-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 bussesDo not interleave write commands with other commands, such as READ Drive-related factorsFormat-related factors Page 34 Factors affecting performance Cartridge Memory LTO-CM 5 Supporting Ultrium featuresAutomation interface Further informationAutomation/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 Supporting the ACI protocol Further detailsRecommended ACI time-out values 42 Supporting Ultrium featuresTreatment of reserved fields Recommended power-up sequenceRecommended load-unload configuration Recommended Get Drive Status polling frequency Firmware upgrade via tapeACI protocol communications retry Upgrading the drive firmwareFirmware upgrade via ACI Firmware upgrade via the primary host interfaceLibrary firmware upgrade via tape Handling irregular cartridgesExpired cleaning cartridge HP-configured or Universal Cleaning cartridge HP-configured or UniversalNon-HP Ultrium 1 cleaning cartridge Unreadable data cartridgeData cartridge with unreadable CM Valid firmware upgrade cartridgeCartridge fails to seat or load Cartridge cannot be loadedCleaning 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 lineControlling data compression Accessing Cartridge Memory without threading the tapeOther mode page information Buffer size at EW-EOMWrite delay time Rewind on resetPartition size 52 Supporting Ultrium featuresSense keys-actions to take 6 Sense keys and codesAction Console MessageFor 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 applicationConsole Message ActionAction Console MessageAction Physical Additional sense codes-actions to takeEnd-of-Tape reached, unable to fit0h-NO SENSE 2h-NOT READY 1h-RECOVERED ERRORLUN not accessible, port in The software must issue a LOAD before media accessThe command cannot be executed because the specified 60 Sense keys and codesmechanism 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 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 OUTAction 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 successful7h-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 1. Retrieve fault information Typical escalation procedure3. Allow the user to try recovery 4. Allow the user to reset devicesSupporting 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