HP LTO 4 SAS, LTO 4 FC Backup software, Resetting drives, Resetting via the ACI Reset command

Page 50
Resetting drives

Resetting drives

The tape drive can be reset by the automation controller via the ACI Reset command or, in ACI mode, by pulling the ACI_RST_L line low (see “Rear Panel and Connectors”, Chapter 7 of the Hardware Integration Guide, Volume 1 of the HP LTO Ultrium Technical Reference Manual).

Resetting via the ACI Reset command

Two levels of reset via the Automation Interface are provided, namely ACI Reset and Drive Reset. The former resets the Automation Interface port and all SCSI parallel/Fibre Channel ports. The latter is equivalent to a power-on reset. Either reset method will interrupt the interface between the drive and host, with the Drive Reset potentially resulting in no End of Data written to tape.

It is therefore strongly recommended that an ACI reset command is not sent unless all other recovery methods have failed. Note that certain ACI commands (see Table 2 on page 43) can be queued behind outstanding SCSI commands giving the impression that the drive has stopped responding over the Automation Interface bus. (All command packages will be still be ack'ed even though the command will be queued.)

A SCSI interface reset will not affect the Automation interface.

NOTE: Following an upgrade of the drive firmware via either tape or SCSI, the drive will be reset as if it had been powered up.

The implementation details are beyond the scope of this document currently.

Resetting using the ACI_RST_L line

The behavior when the ACI-RST_L line is activated depends on whether the drive is in ACI or ADI mode. In ACI mode activating this line will produce a power-on reset. Activating the ACI_RST_L in ADI mode will simply logout the ADT port.

Further details

•For more information about ACI, see “Automation Control Interface (ACI)” in Chapter 1, “Ultrium Features”, of Background to Ultrium Drives, Volume 6 of the HP Ultrium Technical Manual.

•For more details of hardware integration, see Chapter 5, “Automating Drives”, of Hardware Integration, Volume 1 of the HP Ultrium Technical Manual.

Backup software

You need backup application software that supports your Ultrium drive and tape library. For the latest list of appropriate backup packages, contact your tape library supplier.

Suitable backup applications include driver software that establishes the interface between the tape drive and the software. Applications usually recognize tape drives by their manufacturers’ ID string rather than their model number:

LTO 4 SCSI drive

“HP Ultrium 4-SCSI”

50 Supporting Ultrium features

HP restricted

Page 49 Page 51
Image 50
Page 49 Page 51
Contents HP LTO Ultrium tape drives technical reference manual volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP restrictedLegal and notice information 2 Configuration and initialization Contents1 Designing backup applications 3 Use of tapes5 Supporting Ultrium features 4 Factors affecting performance6 Sense keys and codes 7 Exception handlingHP restricted Documents specific to HP Ultrium drives Related documentsDocumentation map Drives-generalCartridges Installation and configurationOperation InterfaceMaintenance and troubleshooting Dealing with errorsLTO Ultrium features General documents and standardizationOptimizing performance 1 Designing backup applicationsNon-immediate commands Large data transfer sizeInformation in Cartridge Memory Cleaning tape headsManaging the use of tapes Monitoring tape useTapeAlert Design goals for LTO backup applicationsDiagnostic logs Displaying drive informationInclude the capability to download firmware Operating system drivers 2 Configuration and initializationInquiry string recovery SCSI protocol, regardless of transport or interface type Example16 Configuration and initialization Supporting additional LUNs Support for additional LUNEnabling additional LUN support 18 Configuration and initialization 3 Use of tapes Using Cartridge Memory attributesUsing MODE SENSE LTO cartridge memoryInterpreting Log Sense data Tape status and capacityFinding the remaining capacity CDB fields Using the SET CAPACITY commandCommand descriptor block How WORM media works Changes to SCSI commandsWORM media New additional sense codes and TapeAlert flagsSET CAPACITY command Error Usage pageERASE commands rejected Re-writing media labelsUnique media identifier Using CM to check tape integrityBehavior with a missing or inconsistent EOD value Barcode support Responding to Cartridge Memory dataLoad count RWW retry counts Corrective actionDetecting the drive’s speed 4 Factors affecting performanceWays of optimizing performance Ensuring the recommended minimum transfer sizesTime-out values Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Media type identificationHost-related factors Recommended support of log pagesFactors affecting performance where possible or a reasonably sized RAID system. More disks means ExampleRecommendation makes sense to split heavily used FC cards across separate PCI bussesDrive-related factors Do not interleave write commands with other commands, such as READFormat-related factors Page 34 Factors affecting performance Automation interface 5 Supporting Ultrium featuresCartridge Memory LTO-CM Further informationAutomation/Device Interface ADI Slave to a library controller Automation Control Interface ACIModes of usage through ACI SCSI pass-through mode ACI command setACI commands that affect drive streaming performance New features in ACI Backward compatibilitySCSI command Encryption support Recommended ACI time-out values Further detailsSupporting the ACI protocol 42 Supporting Ultrium featuresRecommended power-up sequence Treatment of reserved fieldsRecommended load-unload configuration ACI protocol communications retry Firmware upgrade via tapeRecommended Get Drive Status polling frequency Upgrading the drive firmwareLibrary firmware upgrade via tape Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Handling irregular cartridgesNon-HP Ultrium 1 cleaning cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Unreadable data cartridgeCartridge fails to seat or load Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge cannot be loadedInvalid 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 lineOther mode page information Accessing Cartridge Memory without threading the tapeControlling data compression Buffer size at EW-EOMPartition size Rewind on resetWrite delay time 52 Supporting Ultrium featuresAction 6 Sense keys and codesSense keys-actions to take Console Messagelog 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 applicationAction ActionConsole Message Console MessageConsole Message End-of-Tape Additional sense codes-actions to takePhysical reached, unable to fit0h-NO SENSE 1h-RECOVERED ERROR 2h-NOT READYThe command cannot be executed because the specified The software must issue a LOAD before media accessLUN not accessible, port in 60 Sense keys and codesmechanism tests are being executed. When the tests are 62 Sense keys and codes 3h-MEDIUM ERRORA READ , SPACE , WRITE or WRITE FILEMARKS command Send a console message that an unrecovered error on and the drive. Based on this, ask the user to clean the64 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 codes4h-HW ERROR 68 Sense keys and codes 5h-ILLEGAL REQUESTA MODE SELECT parameter list sent to the drive contains 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 OUTAction 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 successful7h-DATA PROTECTION Action 8h-BLANK CHECK related to a missing EOD data set. The most likely cause Bh-ABORTED COMMANDREAD BUFFER command 76 Sense keys and codes Dh-VOLUME OVERFLOWA WRITE or WRITE FILEMARKS command has encountered 3. Allow the user to try recovery Typical escalation procedure1. Retrieve fault information 4. Allow the user to reset devicesMonitoring the condition of the drive and media Supporting TapeAlertFlags TypePage Page Page Page Page Page Page Designing software to use the TapeAlert log TapeAlert modelsTapeAlert informational exception usage model Reading the TapeAlert logTapeAlert polling usage model Supporting OBDR One-Button Disaster Recovery OBDRResponding to the ‘Clean’ LED Providing pass-through mode Requirements for drivers and logical device managersGlossary see ”read-while-write” Index Page Page HP restricted
Top Page Image Contents