manualshive.com logo in svg

HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module, Technical Reference Manual

Share
Download
HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module Technical Reference Manual Download Page 23

IBM (AIX) 23

IBM
 (AIX

)

The 

n

 in the filename is the instance number assigned to the drive by the 

operating system, where 0 is the first device, 1 is the second and so on.

Rewind on Close

Normally, the drive repositions the tape to BOT (Beginning of Tape) when the 

device file is closed. Using the no rewind option is useful when creating and 

reading tapes that contain multiple files.

Retension on Open

Retensioning consists of winding to EOT (End of Tape) and then rewinding to 

BOT, in order to reduce errors. If this option is selected, the tape is positioned 

at BOT as part of the open process.

Compression

Compression can be disabled or enabled.

Summary of Contents for 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module

Page 1: ...unix configuration guide hp ultrium drives technical reference manual generation 2 SCSI and FC drives volume 5 unix configuration guide Part Number C7379 90900 Volume 5 Edition 5 1 July 2003 ...

Page 2: ...nother language without the prior written consent of Hewlett Packard Copyright 2001 2003 by Hewlett Packard Limited Version Date Changed Pages Edition 1 Feb 2001 All Edition 2 Mar 2002 Reordering Removal of pass through functionality Changes to HP chapter update of ioscan output use of sam to add stape and device files Linux chapter use of sam to add device files Sun chapter using seek and tell ve...

Page 3: ...ume 6 of the HP Ultrium Technical Reference Manual 3 HP Ultrium Technology White Paper which describes the features and benefits of HP Ultrium drives Please contact your HP supplier for copies Documentation Map The following will help you locate information in the 6 volume Technical Reference Manual Drives general Installation and Configuration SCSI Drives FC Drives Connectors 1 HW Integration ch ...

Page 4: ...ernal drives SCSI only 1 HW Integration ch 5 n a In Libraries 1 HW Integration ch 1 In Servers SCSI only 1 HW Integration ch 4 n a In Tape Arrays SCSI only 1 HW Integration ch 3 n a SCSI Drives FC Drives Cartridge Memory LTO CM 2 SW Integration ch 5 6 HW Integration ch 5 Cartridges 1 HW Integration ch 9 1 HW Integration ch 5 Features 6 HW Integration ch 5 Managing the use of cartridges 2 SW Integr...

Page 5: ...only 1 HW Integration ch 3 n a Monitoring drive and tape condition 2 SW Integration ch 7 Software troubleshooting techniques 2 SW Integration ch 1 SCSI Drives FC Drives Error Codes 1 HW Integration ch 10 1 HW Integration ch 6 Handling errors 2 SW Integration ch 5 How error correction works 6 Background ch 4 Logs see the LOG SENSE command 3 SCSI ch 4 Recovering from write and read errors 2 SW Integ...

Page 6: ...General Documents can be obtained from Cartridge Memory LTO CM s 1 HW Integration ch 2 2 SW Integration ch 5 6 HW Integration ch 5 Data Compression how it works 6 Background ch 5 Data Compression managing 2 SW Integration ch 5 Design principles 6 Background ch 1 OBDR and CD ROM emulation 6 Background ch 1 2 SW Integration ch 7 Performance optimization 1 HW Integration ch 8 n a 2 SW Integration ch ...

Page 7: ...7 ECMA 114 Rue du Rhône CH 1204 Geneva Switzerland Tel 41 22 849 6000 Web URL http www ecma ch Global Engineering Documents 2805 McGaw Irvine CA 92714 USA Tel 800 854 7179 or 714 261 1455 ...

Page 8: ...8 ...

Page 9: ...ary 11 Backup Applications 12 2 2 2 2 HP UX Systems 13 HP Servers and Workstations HP UX 11 x 13 Introduction 13 Determining the SCSI ID 13 Creating the Device Files 15 What Next 18 3 3 3 3 HP Compaq Tru64 UNIX 19 HP Compaq Tru64 UNIX 5 x 19 What Next 20 4 4 4 4 IBM AIX 21 Determining the SCSI ID 21 Configuring the Device Files 21 Device Filenames under AIX 22 5 5 5 5 Linux 25 Determining the SCSI...

Page 10: ... of mt 27 What Next 27 6 6 6 6 Sun Systems Solaris SunOS 5 x 29 Determining the SCSI ID 29 Configuring the Device Files 30 HP Data Values 32 7 7 7 7 Verifying the Installation 35 Verifying the Installation of the Drive UNIX 35 To verify the installation 35 Glossary 39 Index 43 ...

Page 11: ...s HP UX Chapter 2 3 HP Compaq Tru64 UNIX Chapter 3 3 IBM AIX Chapter 4 3 Linux Chapter 5 3 Sun Systems Solaris 2 SunOS 5 x Chapter 6 For platforms not mentioned here please contact HP because there may be new connectivity details available that arrived after the release notes were published See Chapter 7 for details of how to verify the installation Ultrium Drives in a Library Ultrium drives may a...

Page 12: ...se environment and have been tested with Ultrium drives They use the operating system s standard built in device drivers as described in this manual For further information about optimizing performance and making full use of the drive s functions please contact the software manufacturer or HP 1 Cell Manager is only available on HP UX or Windows 2 Redhat Server only not Caldera Suse and so on HP UX...

Page 13: ...ique for each device attached to the SCSI bus To list the existing devices use the following command sbin ioscan f The output of this should look similar to the following example Class I H W Path Driver S W State H W Type Description bc 0 root CLAIMED BUS_NEXUS bc 1 8 bc CLAIMED BUS_NEXUS Psudo Bus Converter ba 0 8 0 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge ext_bus 1 8 0 2 0 c720 CLAIMED INTERFA...

Page 14: ...e 4 in the I field represents the instance of the SCSI tape driver not the SCSI ID tape 4 2 0 1 5 0 stape CLAIMED DEVICE HP Ultrium Note If you are installing the drive onto a Storage Area Network SAN the fibre channel SCSI bridge will also appear in the list of attached devices If you cannot find the Ultrium drive this may be because the kernel does not contain the correct driver Use the System A...

Page 15: ...m or by executing the mksf command To add device files using sam This is the recommended and simplest way to create device files 1 sam This will bring up the graphical user interface for the utility 2 Select the following Peripheral Devices Tape Drives sam will then scan the system for any tape drives connected When an HP Ultrium drive is found it will be displayed as Hardware Path Driver Descript...

Page 16: ...on rewind driver Berkeley encoding rewind driver Berkeley encoding rewind driver where X Y Z cXtYbZBEST cXtYbZBESTb cXtYbZBESTn cXtYbZBESTnb is the card number is the target number is the LUN number Best compression driver AT T encoding with rewind Best compression driver Berkeley encoding with rewind Best compression driver AT T encoding non rewind Best compression driver Berkeley encoding non re...

Page 17: ...er indicates AT T mode Berkeley and AT T modes differ in their read only close behavior 3 In Berkeley mode the tape position will remain unchanged by a device close operation 3 In AT T mode a device close operation will cause the tape to be repositioned just after the next tape filemark the start of the next file In most cases Berkeley mode should be used dev rmt X name Specifies the path of the d...

Page 18: ...le for Ultrium in uncompressed mode you should use a command such as mksf H a b U_18 and for compressed mode default mksf H a b U_18C The hardware path can be found from previous ioscan output What Next Once the device files have been created you should confirm that your new tape drive is working properly Chapter 7 Verifying the Installation provides instructions on backing up and restoring a samp...

Page 19: ...ransferSize 0xffffff 16Mb 1 ReadyTimeSeconds 120 Seconds SyncTransfers enabled WideTransfers enabled InquiryLength 0x20 DENSITY DensityNumber 0 1 2 3 4 5 6 7 OneFileMarkOnClose yes DensityCode 0x42 Blocking 0 CompressionCode 1 Buffered 1 Speed 0 MODESELECT ModeSelectNumber 0 SavePage No PageFormat scsi2 BlockDescriptor yes TransferLength 16 Hdr Tape BufferMode 0x1 Hdr MediumType 0 Data UBYTE 0 0x3...

Page 20: ...y are no rewind devices Those in dev tape will do a rewind on close The device files then have the syntax tapeX_dn For example dev ntape tape66_d1 is a device file for device 66 no rewind using density number 1 Since all density numbers have the same parameters it does not matter which density number file is used What Next Once the device files have been created you should confirm that your new ta...

Page 21: ...the series 00 00 0S X 0 where X is the SCSI ID Review the list of existing SCSI IDs and choose an available ID to assign to the new tape drive Configuring the Device Files To install an HP Ultrium drive on an IBM workstation you will need to create the appropriate device files for the drive Note Do not choose the smit option of 4mm2gb as the Tape Device Type This is reserved for Connor drives If y...

Page 22: ...trium drives will work with tar cpio backup restore and dd For systems other than the 43P the drive is also boot capable provided a boot tape is generated using mkszfile and mksysb Once the device files have been created you should confirm that your new tape drive is working properly Chapter 7 Verifying the Installation provides instructions on backing up and restoring a sample file to test your i...

Page 23: ... tape to BOT Beginning of Tape when the device file is closed Using the no rewind option is useful when creating and reading tapes that contain multiple files Retension on Open Retensioning consists of winding to EOT End of Tape and then rewinding to BOT in order to reduce errors If this option is selected the tape is positioned at BOT as part of the open process Compression Compression can be dis...

Page 24: ...24 IBM AIX ...

Page 25: ...nel 00 Id 00 Lun 00 Vendor HP Model Type Direct Access ANSI SCSI Revision 02 Look at the ID information to establish which IDs are in use Configuring on Linux Systems No changes are needed to support Ultrium on Linux platforms however you should ensure that you have the relevant drivers loaded To see the device drivers loaded currently execute an lsmod command this will give output like Module Siz...

Page 26: ...he tape driver at module load time execute dmesg grep st This should find a number of lines One should look like Detected SCSI tape st0 at scsi1 channel 0 id 5 lun 0 To load the tape driver module if it is not loaded as above execute insmod st to load it This should happen naturally if your system is rebooted after attaching the drive When the ST driver module has been added a list of tape device ...

Page 27: ... of mt you must tell the st driver that HP Ultrium drives use logical block addressing You can do this by using the command mt f device file stsetoptions scsi2logical where dev stp is the device file Note however that this information is not preserved across reboots so you need to execute this command each time the system comes up The stinit utility offers a convenient way of handling this see the...

Page 28: ...28 Linux ...

Page 29: ... 501c8000 9e70 6 1 fas FAS SCSI Host Bus Adapter Drive This indicates that there are two SCSI controllers on the system an ESP based adapter and a FAS based adapter For the adapter to which the new tape drive is attached you will need to determine what SCSI IDs are already used For newer LSI Intraserver LVD SCSI controllers modinfo grep Interserver This will produce output similar to the following...

Page 30: ...aining st 2 0 This might be as follows but on a single line lrwxrwxrwx 1 root root 63 Mar 1 00 00 dev rmt 0m devices sbus 1f 0 espdma e 8400000 esp e 8800000 st 2 0 m Here you could use dev rmt 0m shown underlined above as the device file Only if necessary make the following file modifications to enhance performance 1 In the file kernel drv st conf after these lines Copyright c 1992 by Sun Microsy...

Page 31: ... you are replacing an existing tape device on the same SCSI ID remove the contents of the dev rmt directory as follows cd dev rmt rm 3 Do a reconfigure boot cd touch reconfigure sync halt 4 When the system is down reboot boot r Make sure you include the r switch so that the device directory is reconfigured using the new data 5 You should now be able to use the drive Use dev rmt Xcb if you require ...

Page 32: ...hat this is the first version type 0x36 The value for an Ultrium drive in usr include sys mtio h This indicates a type of MT_ISOTHER in other words not any of the default types such as DAT or DLT bsize 0 Indicates variable block size options 0xd639 This value is derived from constants provided in usr include sys scsi targets stdef h The value determines which operations the driver can perform with...

Page 33: ...record length bsf and bsr enabled long timeouts for erase EOD recognition Unloadable device driver 5 x longer timeouts buffer writes and pre acknowledge sucess variable records not limited to 64 KB and for Solaris 9 only auto density over ride and MODE SELECT compression no of densities 4 There are four densities following in the parameter list density n 0x00 Creates a device file with compression...

Page 34: ...34 Sun Systems Solaris SunOS 5 x ...

Page 35: ...st data to a tape 3 Read the test data from the tape 4 Compare the data read from the tape with the original data on disk To verify the installation 1 Test the SCSI connection to the tape drive by doing a rewind operation a If there is a tape cartridge already in the drive remove it b Insert a tape cartridge c Rewind the tape using the command line mt f device file rewind For example on HP UX mt f...

Page 36: ...s extract from the archive Use the same value for the device file argument as in step 2 6 Compare the original with this retrieved file cmp original file tmp retrieved file This step compares the retrieved file and the original file byte by byte If they are the same there should be no output and this verifies that the installation is correct The arguments are as follows c Create a new archive back...

Page 37: ...ould be as follows 1 Change directory to root cd 2 Back up stand vmunix to tape tar cvf dev rmt 0m stand vmunix Note the prefix of to the filename 3 Change to the temporary directory cd tmp 4 Extract the file from the tape tar xvf dev rmt 0m 5 Compare the original with the restored version cmp stand vmunix tmp stand vmunix Note that the original filename is not prefixed with ...

Page 38: ...38 Verifying the Installation ...

Page 39: ... of redundant information in order to reduce the number of bits required to represent the data This is basically done by representing strings of bytes with codewords In Ultrium drives the data is compressed using the LTO DC compression format which is based on ALDC licensed from Stac IBM with two enhancements One limits the increase in size of data that cannot be compressed that ALDC produces The ...

Page 40: ... to 2 Gb s and network functionality in a single connectivity technology filemark A mark written by the host to the tape that can be searched for often using the drive s fast search capability It does not necessarily separate files It is up to the host to assign a meaning to the mark immediate mode A mode of responding to SCSI commands where the drive or other peripheral does not wait until the co...

Page 41: ...vel along two wires and the difference in voltage between the wire pairs determines the signal value This enables faster data rates and longer cabling with less susceptibility to noise than SE signaling and reduced power consumption Narrow and Wide Fast Ultra and Ultra2 SCSI Narrow SCSI devices can transfer data one byte at a time and are sometimes called 8 bit SCSI devices They can conform to eit...

Page 42: ...Ultrium drives are Ultra2 wide SCSI 3 compatible devices They can be used with both LVD and SE host bus adapters sequential access Sequential access devices store data sequentially in the order in which it is received Tape devices are the most common sequential access devices Devices such as disk drives are direct access devices where data is stored in blocks not necessarily sequentially Direct ac...

Page 43: ...tations 30 direct access 42 documents related 3 F F F F fast SCSI 41 fibre channel 40 filemarks 40 filenames under AIX 22 H H H H HP Compaq Tru64 19 HP UX systems 13 determining SCSI ID 13 device files 15 I I I I IBM AIX 21 determining SCSI ID 21 device files 21 immediate mode 40 infinite flush 40 installation verifying 35 L L L L Linux 25 determining SCSI ID 25 LUN 40 LVD SCSI 41 M M M M mode AT ...

Page 44: ...42 single ended SCSI 41 Solaris 29 storage area network 41 Sun workstations 29 data values 32 determining SCSI ID 29 device files 30 synchronous data transfer 39 systems HP UX 13 Linux 25 T T T T Tru64 19 U U U U ultra SCSI 41 V V V V verifying installation 35 W W W W wide data transfer 39 wide SCSI 41 workstations Sun 29 ...

Reviews:

No comments

Brands by name

Popular brands

Load more brands