HP LTO 4 FC, LTO 4 SCSI manual Factors affecting performance, Ways of optimizing performance, page

Page 27
4 Factors affecting performance

4 Factors affecting performance

This chapter contains techniques and information to help you design software applications so that they use the tape drive’s potential as efficiently as possible.

Ways of optimizing performance:

 

Ensuring the recommended minimum transfer sizes

page 27

 

Identifying the media type page 28

 

 

Using Cartridge Memory instead of tape headers

page 28

 

Using the Performance Log page to diagnose problems page 28

Time-out values to help you tune timings in backup applications page 28

Log pages—recommended support page 29

 

Factors affecting performance, relating separately to the host, drive and format page 29

Ways of optimizing performance

HP’s Ultrium drives are high-performance products. Application software may require significant enhancement in order to capitalize on this speed. There are a number of areas to look at and these are discussed below.

Further details can also be found in the “How to optimize the performance of hp ultrium tape drives” white paper.

Detecting the drive’s speed

Applications should not key off Inquiry strings in order to tell the difference between different speed drives. It is better to use the Performance Log page see under the LOG SENSE command in Chapter 4, “Commands”, of SCSI Interface, Volume 3 of the HP LTO Ultrium Technical Reference Manual.

In the Performance Log page (34h), parameter 04h (Native data rate) gives the native data rate of the drive in units of 100 KB/s. LTO 4 drives give the value 04B0h, indicating 120 MB/s with Ultrium 4 media or no cartridge loaded. If a previous generation cartridge is loaded, the value will be lower.

Ensuring the recommended minimum transfer sizes

Use the Data Compression Log page. HP cannot diagnose performance issues without accurate reporting of the current compression or the average compressibility over a backup session. Make sure that you report the log page.

Regarding HP’s One-Button Disaster Recovery (OBDR) feature (see “One-Button Disaster Recovery (OBDR)” on page 89), it is important to note that in some situations the SCSI block size may have to be fixed for a given tape for format reasons. This means that if the host writes 2 KB blocks to support OBDR, it may have to continue to write 2 KB blocks for the rest of the tape; it depends on the format compatibility required by the overall system. However as HP Ultrium drives are insensitive to

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

Image 27
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 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 LTO cartridge memory Using Cartridge Memory attributesUsing MODE SENSE 3 Use of tapesTape status and capacity Finding the remaining capacityInterpreting Log Sense data Using the SET CAPACITY command Command descriptor blockCDB 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 commandUsing 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 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 valuesRecommended support of log pages Factors affecting performanceHost-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 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 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 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 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 5h-ILLEGAL REQUEST A MODE SELECT parameter list sent to the drive contains68 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 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 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 logReading 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 modeGlossary see ”read-while-write” Index Page Page HP restricted