HP 157770-001 - DAT Drive 20/40 Tape Configuration Manual
Dds/dat evolution ii drives
Hide thumbs
Also See for 157770-001 - DAT Drive 20/40 Tape:
- User manual (74 pages) ,
- Start here (2 pages)
Table of Contents
Advertisement
Quick Links
HP DDS/DAT drives
UNIX, Linux and OpenVMS configuration guide
DDS/DAT Evolution II drives:
HP DDS-4 drive (40 GB)—USB and SCSI
HP DAT 72 drive (72 GB)—USB, SCSI and SAS
HP DAT 72 autoloader (720 GB)—SCSI
HP DAT 160 drive (160 GB)—USB, SCSI and SAS
HP DAT 320 drive (320 GB)—USB
30 Mar 07
Part number: DW049-90915
Edition 1: May 2009
Advertisement
Table of Contents
Related Manuals for HP 157770-001 - DAT Drive 20/40 Tape
Summary of Contents for HP 157770-001 - DAT Drive 20/40 Tape
- Page 1 HP DDS/DAT drives UNIX, Linux and OpenVMS configuration guide DDS/DAT Evolution II drives: HP DDS-4 drive (40 GB)—USB and SCSI HP DAT 72 drive (72 GB)—USB, SCSI and SAS HP DAT 72 autoloader (720 GB)—SCSI HP DAT 160 drive (160 GB)—USB, SCSI and SAS HP DAT 320 drive (320 GB)—USB 30 Mar 07 Part number: DW049-90915...
- Page 2 Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
-
Page 3: Table Of Contents
Contents About this guide ..........5 Related documents . - Page 4 Using the seek and tell features of mt ......... 30 Configuring non-compression device files .
-
Page 5: About This Guide
About this guide NOTE: DDS/DAT Evolution II drives, available with USB 2.0, U160 SCSI or SAS1.1 interfaces, are identifiable by the round LEDs on the front panel, as opposed to rectangular or oval. USB and SAS drives are only supported on Linux (and Windows). This guide contains information on connecting to various operating systems. -
Page 6: Usb Specifications
Copies of General Documents can be obtained from: INCITS 1 1 West 42nd Street, New York, NY 10036-8002, USA CP 56, CH- 1 21 1 Geneva 20, Switzerland ECMA 1 14 Rue du Rhône, CH- 1 204 Geneva, Switzerland Tel: +41 22 849 6000 Web URL: http://.www.ecma.ch Global Engineering... -
Page 7: Introduction
Introduction Drivers and backup software Drivers All supported UNIX operating systems provide native driver support for HP DDS/DAT tape drives. In some cases the drivers require configuration to perform optimally. UNIX applications You can write scripts to control DDS/DAT drives in UNIX using standard backup utilities such as . - Page 8 Introduction...
-
Page 9: Hp (Hp-Ux) Servers And Workstations
HP (HP-UX) servers and workstations This chapter covers: • HP servers and workstations: HP-UX 1 1i v1 (1 1.1 1), 1 1i v2 (1 1.23) • HP servers: HP-UX 1 1i v3 (1 1.31) NOTE: Only SCSI tape drives and autoloaders are supported on HP-UX. Introduction Before you install your tape drive log on to the HP web site, www.hp.com, and download the latest hardware enablement (HWE) patch bundle for your operating system. - Page 10 0 0/0/1/0 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035) 1 0/0/1/1 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035) 2 0/0/1/2 UsbEhci CLAIMED INTERFACE PCI SerialBus (103300e0) sideba 0 0/0/2/0 side_multi CLAIMED INTERFACE CMD IDE controller ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE Primary Channel 3 0/3 CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
-
Page 11: Adding Stape And Schgr (Autoloader Driver) To The Kernel
/dev/rtape/tape0_BEST /dev/rtape/tape0_BESTb /dev/rtape/tape0_BESTn /dev/rtape/tape0_BESTnb tape 64000/0xfa00/0x1a estape CLAIMED DEVICE online SDLT600 0/2/1/0.0x3.0x0 /dev/rtape/tape12_BEST /dev/rtape/tape12_BESTb /dev/rtape/tape12_BESTn /dev/rtape/tape12_BESTnb For a particular SCSI device, you can decode the SCSI bus ID and the drive’s SCSI ID and LUN ID from the lunpath hardware path. For example: Class Lun H/W Path Driver... - Page 12 Use the ‘ ’ utility. Sam runs as a mouse-driven GUI (Figure 1) on a system with full graphics capability, or as a console text-based interface (Figure 2). If you use the text-based interface, use the Tab and arrow keys to navigate, and the Return key to select. SAM GUI Figure 1 Figure 2...
- Page 13 Kernel Configuration Drivers Highlight the driver. If the driver has not been added to the kernel, both Current State and stape Pending State will read “Out”. Select the following: Actions Add Driver to Kernel The Pending State will now read “In”. To add the new driver to the kernel, select: Actions Create a New Kernel...
- Page 14 From the SMH Tools page (see Figure 3), select Modules from the Kernel Configuration section. Figure 3 SMH web-based interface (HP-UX1 1i v3) In the Search box on the Kernel Configuration page, type and execute the search. stape The search results list will include both modules.
-
Page 15: Add Device Files
On the Modify Kernel Module: estape page, for Next Boot State, select the “static” radio button. Check the box entitled Backup to create a backup copy of the existing kernel (see Figure Figure 4 Adding driver to the kernel estape If you wish, type in a Reason for Change, such as “... - Page 16 For example, when an HP DAT160 drive is found, it will be displayed as something like: Hardware Path Driver Description =========================================================== 8/0/2/0.3.0 stape HP DAT160 Highlight the drive and select the following from the tool bar: Actions Create Device Files Create Default Device Files This will create default device files for the drive.
-
Page 17: Configuring An Autoloader
Select from the Class drop down box on the HP-UX Peripheral Device Tool page. Select the tape tape device (radio button) requiring device files from the resulting list. If device files are not already present this will be indicated under the Properties header (see Figure Selecting a tape device to create its device files (Agile View) Figure 5... -
Page 18: What Next
For example, using values from the output above and a LUN of 1, you would execute: ls -al mknod /dev/rac/c4t5d1 c 203 0x045100 To verify that the autoloader has installed correctly, run the following command: mc -p /dev/rac/<device_file> -rIDSM This will display the various elements in the autoloader. This will display the various elements in the autoloader. -
Page 19: Hp (Openvms) Servers And Workstations
HP (OpenVMS) servers and workstations NOTE: Only SCSI tape drives and autoloaders are supported on OpenVMS. Determining attached devices After connecting the tape drive to your system, boot OpenVMS and check for the presence of the new tape device. Execute the following commands. $ sho dev mk Device Device... -
Page 20: Verifying The Configuration Of An Autoloader On Openvms And Mru
Verifying the configuration of an autoloader on OpenVMS and To verify the configuration, enter the following MRU command: $ robot show robot gka401 Robot Name: gka401 Type: SCSI Media Robot Identifier: HP DAT Autoloader 1.00 Slots: Drives: Inports: Outports: Transports: For further details on MRU and using the robot commands, see the MRU User Guide. -
Page 21: Hp (Tru64 5.1X) Servers And Workstations
HP (Tru64 5.1x) servers and workstations NOTE: Only SCSI drives and autoloaders are supported on HP Alpha Tru64 systems. Updating the tape driver NOTE: DDS-4 and DAT 72 drives are natively supported on HP Alpha Tru64 v5.1B-2 and above. DAT 160 drives are natively supported on HP Alpha Tru64 V5.1B-3. Steps 1–3 below are only required for earlier versions of Tru64. - Page 22 DENSITY: DensityNumber = 0,3,4,5,6,7 DensityCode = default CompressionCode = 0x0 Buffered = 0x1 DENSITY: DensityNumber = 1,2 DensityCode = default CompressionCode = 0x1 Buffered = 0x1 DAT 72 drives: SCSIDEVICE Type = tape Name = "HP" "C7438A" PARAMETERS: TypeSubClass = rdat TagQueueDepth MaxTransferSize = 0x0ffffff...
- Page 23 MaxTransferSize = 0x0ffffff # (16MB - 1) ReadyTimeSeconds = 120 # seconds Mode select parameters for rewind after reset behavior MODESELECT: ModeSelectNumber = 0 SavePage = No PageFormat = scsi2 BlockDescriptor = yes TransferLength = 16 Hdr.Tape.BufferMode = 0x1 Data.UBYTE[0] = 0x3D #Vendor Unique Page Code 0x3D Data.UBYTE[1] = 0x02 Data.UBYTE[2] = 0x01...
-
Page 24: Configuring An Autoloader
Configuring an autoloader Add the following entries to /etc/mcicap to configure an autoloader: mc0:\ :mc=/dev/changer/mc1:\ :dn=/dev/tape/tape23:tc=DAT Autoloader: # Digital TLZ6L/TLZ7L 4mm DAT Tape Autoloader DAT Autoloader|tlz6l|tlz7l|Digital TLZ6L/TLZ7L|tsl9000|tsl10000:\ :it=scsi2:dt=tape:ae:re: What next? Once the device files have been created, you should confirm that your new tape drive is working properly. -
Page 25: Ibm (Aix) Servers And Workstations
IBM (AIX) servers and workstations NOTE: Only SCSI drives are supported on AIX . Determining the SCSI ID Before you configure your system to support your drive, determine which SCSI ID to use. IDs must be unique for each device attached to the SCSI bus. To list existing devices, use the following: % lsdev -C |grep SCSI This produces output similar to: scsi0 Available 00-00-0S Standard SCSI I/O Controller... - Page 26 A pop-up window is displayed: Select “ ” or “ ” as the tape drive you wish to change. Other SCSI tape drive If no device has been configured at this address before, choose connection addresses as appropriate. The following details are displayed: Check the following values and change them if necessary: •...
-
Page 27: If You Are Using A Non-Graphics Terminal
If you are using a non-graphics terminal At the command line type: % smit -C tape The following is displayed: If no device has been configured at this address before, select “ ” to set up the add a tape drive address. -
Page 28: Device Filenames Under Aix
HP DDS-format drives will work with . For systems other than the 43P, cpio backup restore the drive is also boot-capable, provided a boot tape is generated using mkszfile mksysb Once device files have been created, you should confirm that your new tape drive is working properly. Chapter 8, “Verifying the installation”... -
Page 29: Linux (Kernel 2.6.X) Servers And Workstations
Linux (kernel 2.6.x) servers and workstations NOTE: USB, SCSI and SAS drives are supported on Linux kernel 2.6.x. Determining the SCSI ID Look at the output of to find out what SCSI channel number is used for each connection. dmesg To find out the SCSI IDs in use on each channel, type: cat /proc/scsi/scsi This will produce output similar to the following for each device:... -
Page 30: Using The Seek And Tell Features Of Mt
available as either loadable modules (for example, usable with and visible with ) or insmod lsmod are statically built into your kernel. NOTE: To add drivers to the statically built kernel you need the Linux source code available on disk and knowledge of how to use the kernel building tools that ship with various Linux distributions. -
Page 31: Configuring Non-Compression Device Files
this; see the relevant man page for more information. If you use this approach, set stinit.def as described in the next section, ”Configuring non-compression device files”. Configuring non-compression device files The following process allows the use of non-compression device files. HP recommends the use of files with the mode identifier of “m”... -
Page 32: Installing Usb Drivers On Linux
Installing USB drivers on Linux Two drivers are required in order to use HP DDS/DAT USB tape drives. These are included with the operating system and should be loaded automatically. Use the following procedure to check that both drivers are present: usb_storage driver At the command prompt type: lsmod | grep usb_storage... -
Page 33: Sun (Solaris) Servers And Workstations
Sun (Solaris) servers and workstations NOTE: Only SCSI drives are supported on Solaris. Determining the SCSI ID Before you configure your system to support a DDS-format drives, you need to determine which SCSI ID to use. IDs must be unique for each device on attached to the SCSI bus. Use the command to identify SCSI controller drivers installed on the system. -
Page 34: Hp-Data Values
for Solaris 9 and 10 (and 8 with the latest st patch): tape-config-list = "HP DAT160","HP DAT160 tape drive","HP-DAT160"; HP-DAT160 = 1,0x34,0,0x18679,1,0x00,0,60,300,600,1200,600,600,18000; name="st" class="scsi" target=X lun=0; tape-config-list = "HP C7438A","HP DAT72 tape drive","HP-DAT72"; HP-DAT72 = 1,0x34,0,0x18679,1,0x00,0,60,300,600,1200,600,600,18000; name="st" class="scsi" target=X lun=0; tape-config-list = "HP C5683A","HP DDS-4 tape drive","HP-DDS-4";... - Page 35 The syntax for on Solaris 9, 10 (and 8 with the latest st patch) HP-DDS-4 HP-DAT72 HP-DAT160 <drive type> = <version>, <type>, <bsize>, <options>, <no. of densities>, <density 0>, <density 1>, ..., <density n>, <default density>, <non-motion timeout>, <read/write timeout>, <rewind timeout>, <space timeout>, <load timeout>, <unload timeout>, <erase timeout>...
-
Page 36: Configuring An Autoloader
Parameter Value Meaning Supported density code. The value of means use the default density <density n> 0x26 0x00 chosen by the drive—which is for DDS-4, for DAT 72 and 0x47 0x26 0x47 0x48 for DAT 160. 0x48 0x00 Density 0 ( for DDS-4, for DAT 72 and for DAT 160) is the... -
Page 37: Verifying The Installation
Verifying the installation As part of the installation process, you will have installed the appropriate device driver for your UNIX system, and created device files to communicate with the tape drive. This section describes how you can verify that the installation has been performed correctly. In outline, the procedure is as follows: Write test data to a tape. -
Page 38: Example
NOTE: Make sure you prefix the file name with ‘ ’ when you back it up to tape. If you do not, the restore operation in step 3 will overwrite the original copy on disk. Read the file back from tape: % cd /tmp % tar xvf <archive name>... -
Page 39: Glossary
Glossary AT&T mode Berkeley and AT&T functional modes differ in “read-only” close functionality. In AT&T mode, a device close operation will cause the tape to be repositioned just after next filemark on the tape (the start of the next file). Berkeley mode Berkeley and AT&T functional modes differ in “read-only”... - Page 40 Digital Data Storage is a recording format that builds on the DAT format to support the storage of computer data. It was developed originally by Hewlett-Packard and Sony as an industry standard. The first generation standard was DDS- 1 (or simply DDS), to which was added data compression to produce the DDS-DC standard.
-
Page 41: Index
Index agile addressing group applications asynchronous data transfer HP HP-UX workstations and servers AT&T mode HP OpenVMS servers and workstations autoloaders HP Tru64 5.1x servers and workstations application software HP-data values for Sun Solaris detecting LUNs in Linux HP-UX systems HP-UX systems:determining attached devices backup software Berkeley mode... - Page 42 verifying autoloader configuration OpenVMS servers and workstations determining attached devices partitions persistent dsf records related documents SAS compliance SCSI SCSI ID, determining IBM (AIX) Linux Sun workstations sequential access servers HP OpenVMS IBM AIX Linux software, backup Solaris Sun workstations determining SCSI ID synchronous data transfer UNIX scripts...