HP DDS/DAT tape drives UNIX, Linux and OpenVMS configuration guide Abstract DDS 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 and SAS This guide provides basic information on configuring the drives with various operating systems.
Legal and notice information © Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Windows is a U.S.
Contents 1 Introduction ....................................................................................... 6 Purpose of this manual ................................................................................................................ 6 SAS drives ........................................................................................................................... 6 Backup applications .......................................................................................................
Configuring non-compression device files ..................................................................................... 32 Verifying an autoloader has installed correctly .............................................................................. 32 What next? .............................................................................................................................. 32 7 Sun (Solaris) servers and workstations .................................................
Figures 1 SAM GUI ................................................................................................................. 9 2 SAM text-based interface ......................................................................................... 10 3 SMH web-based interface (HP-UX11i v3) ................................................................... 11 4 Adding estape driver to the kernel .............................................................................
1 Introduction Purpose of this manual This manual provides basic information on configuring the drives with various operating systems. See the top-level release notes that accompany the drive for expected functionality and features. HP DDS/DAT drives are supported on the following platforms: • • • • HP (HP-UX) servers and workstations, page 7 HP (OpenVMS) servers and workstations, page 17 HP (Tru64 5.1x) servers and workstations, page 19 IBM (AIX) servers and workstations, page 23 • Linux (kernel 2.
2 HP (HP-UX) servers and workstations For supported versions of HP-UX, go to http://www.hp.com/go/connect. NOTE: A block size no larger than 256 KB is strongly recommended when working with HP-UX. See “Using large block sizes” on page 14. Before you install your tape drive, visit the HP web site, www.hp.com, and search to locate IT Resource Center (you may be required to set up a new login). Download the latest hardware enablement (HWE) patch bundle for your operating system.
OO disk OO OO OO ba slot slot graphics ba slot ba ba slot ba slot escsi_ctlr ext_bus target disk slot lan lan ba slot ba ba ba ba slot ba slot escsi_ctlr ext_bus target tape ba ba slot processor processor ba ipmi tty acpi_node 15 5 16 5 12 1 0 1 0 2 2 3 4 3 5 4 0 0 1 2 5 0 1 6 6 7 8 9 10 7 11 8 1 1 0 8 12 13 9 0 1 14 0 3 0 0/0/2/1.0.0 UsbBulkOnlyMS CLAIMED 0/0/2/1.0.16 UsbScsiAdaptor CLAIMED 0/0/2/1.1 UsbMiniBus CLAIMED 0/0/2/1.1.
• Tape drive SAS address (hexadecimal) = 0x500110a0013091b8 • Tape drive SCSI LUN = 0x0 (hexadecimal SCSI-3 64-bit LUN identifier) Similarly, for a given FC device the FC bus ID, the World Wide Name (WWN) and the LUN ID can be decoded from the Lun H/W Path. For example: If the lunpath hardware path for a giventape drive is “0/4/1/0.0x50060b0000b7f3c8.0x0”. • The FC bus ID is “0/4/1/0” (including all the numbers separated by “/”). From the remaining “0x50060b0000b7f3c8.
Figure 2 SAM text-based interface . 1. Enter sam at the command line. % sam 2. Select the following: Kernel Configuration > Kernel Configuration (character mode) > Modules 3. Highlight the stape driver. If the driver has not been added to the kernel, both Current State and Planned State will read “unused”. 4. Type “m to modify the stape driver and “s” to set it to “static”. The Planned State will now read “static”. 5. The stape driver is now added to the kernel. 6.
2. From the SMH Tools page, select Modules from the Kernel Configuration section: Figure 3 SMH web-based interface (HP-UX11i v3) . 3. In the Search box on the Kernel Configuration page, type stape and execute the search. The search results list will include both estape and stape modules. If either of these modules is not installed both Current State and Next Boot State will be shown as “unused”. A state of “static” indicates that the module is installed. 4. Select the estape module3 radio button.
6. If you wish, type in a Reason for Change, such as “Initial estape installation May 1st 2007” and then select the Modify tab. 7. Click the OK button at the Operation Successful page. Both estape and stape drivers will now be shown with Next Boot State as “static”. 8. For media changers, use a similar procedure to prepare the eschgr (with schgr) module. 9. From the right-hand panel on the Kernel Configuration page, click View Pending Changes and reboot and proceed to reboot the system as directed.
4. When you have exited sam, run ioscan to see the tape drive: %/sbin/ioscan -fnC tape All default device files displayed have compression enabled. NOTE: HP recommends the ‘Berkeley’ device files of most applications: cXtYdZBESTnb = Berkeley, no rewind, best available density cXtYdZBESTb = Berkeley, with rewind, best available density where: X = card number Y = target number Z = LUN number nl nl nl nl nl nl For HP-UX 11i v3 (HP-UX 11.31) 1.
Using large block sizes A block size no larger than 256 KB (262144 bytes) is strongly recommended when working with HP-UX and tape or VTL devices. Backup applications should be configured to work with I/O block sizes that are no larger than 256 KB. Please check your application documentation to find out how to check or configure block sizes used for transfers to and from tape or VTL devices.
What next? Once the device files have been created, you should confirm that your new tape drive is working properly. “Verifying the installation” on page 39 provides instructions on backing up and restoring a sample file to test your installation.
HP (HP-UX) servers and workstations
3 HP (OpenVMS) servers and workstations NOTE: SAS drives are not supported on Alpha Server systems. 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.
2. Enter the following, replacing gka401 with the changer device file you found in step 1: $ mcr sysman io connect gka401: /driver=sys$gkdriver.exe/noadapter $ define/system mru_robot gka401 To maintain these changes across reboots, edit the sys$startup_vms.com file to include these two lines.
4 HP (Tru64 5.1x) servers and workstations NOTE: Only SCSI drives and autoloaders are supported on HP Alpha Tru64 systems. DAT 320 drives are not supported. 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. 1. Versions of Tru64 before v5.1B-2 only (v5.
2. Versions of Tru64 before v5.1B-2 only (v5.1B-3 for DAT 160 drives): Add the following entry to your /etc/ddr.
TransferLength = 16 Hdr.Tape.BufferMode = 0x1 Data.UBYTE[0] = 0x3D #Vendor Unique Page Code 0x3D Data.UBYTE[1] = 0x02 Data.
4. The names of the device files can be interpreted as follows: Devices in the /dev/ntape directory are "no-rewind" devices, those in /dev/tape will do a rewind on close. The device files then have the syntax, tapeX_dn where: X is the instance of the drive n is the density number nl 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.
5 IBM (AIX) servers and workstations For supported versions of AIX, see http://www.hp.com/go/connect.
3. A pop-up window is displayed: Select the tape drive you wish to change. The example above shows a DDS/DAT tape drive as available for selection.
4. The following details are displayed: Check the following values and change them if necessary: • • • • BLOCK Size (0=variable length)= 0 Use EXTENDED file marks = “no” RESERVE/RELEASE support = “yes” Set timeout for the READ or WRITE command = 1200 Click on the “OK” button to apply the changes. If you are using a non-graphics terminal 1.
2. The following is displayed: Select “change/show characteristics of a tape drive” 3. A pop-up window is displayed: Select the tape drive you wish to change. The example above shows a DDS/DAT tape drive as available for selection. 4.
Device filenames under AIX Use device filenames as listed below for the combination of Rewind on Close, Retension on Open, and Compression that you want: Filename Rewind on Close Retension on Open Compression /dev/rmtn Yes No enabled /dev/rmtn.1 No No enabled /dev/rmtn.2 Yes Yes enabled /dev/rmtn.3 No Yes enabled /dev/rmtn.4 Yes No disabled /dev/rmtn.5 No No disabled /dev/rmtn.6 Yes Yes disabled /dev/rmtn.
IBM (AIX) servers and workstations
6 Linux (kernel 2.6x) servers and workstations NOTE: USB, SCSI and SAS drives are supported on Linux kernel 2.6.x. Ensure the correct HBA and driver are installed NOTE: HP recommends using the HP driver for your HP branded SAS Host Bus Adapter. HP Host Bus Adapter drivers enable unique features in HP SAS tape drives that improve their compatibility and data reliability. The native Host Bus Adapter driver (which may be included with your Linux operating system) may not take full advantage of these features.
For example, the st driver for tape listing would resemble the entry shown below. Also shown below are two examples of HBA drivers—cciss driver (for HP SmartArray SAS HBAs) and mptsas driver (for LSI SAS HBA): Module Size Used by st 38749 0 . . cciss 68484 3 . . mptsas 37321 0 If a particular driver module is not listed as above use the modprobe utility to load it.
TIP: You may prefer to redirect a lengthy dmesg output to a file for browsing at your convenience: dmseg > my_boot_messages.txt or pipe the output of dmesg to a page scrolling utility dmesg | more Extract from dmesg output: . . scsi3 : cciss Vendor: HP Model: DAT320 Rev: ZxxD Type: Sequential-Access ANSI SCSI revision: 06 scsi 3:0:0:0: Attached scsi generic sg0 type 1 st: Version 20050830, fixed bufsize 32768, s/g segs 256 st 3:0:0:0: Attached scsi tape st0 . .
Where stinit is available, you can also re-initialize the drive to new parameters as entered in / etc/stinit.def without reboot by running: stinit 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” (such as /dev/nst0m). This sets the mode to non-compression, and the blocksize to variable. 1. Install mt-st if not already installed. You can find this on the Linux installation CD/DVD.
7 Sun (Solaris) servers and workstations For supported Solaris versions, go to http://www.hp.com/go/connect. 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. 1. Use the modinfo command to identify SCSI controller drivers installed on the system.
1. In the file /kernel/drv/st.conf, after these lines: ######## # Copyright (c) 1992, by Sun Microsystems, Inc. #ident "@(#)st.conf 1.
HP-data values The values for the parameters, which provide normal DDS mode, have the following meanings. The syntax for HP-DDS-4, HP-DAT72, HP-DAT160 and HP-DAT320 on Solaris 9, 10 (and 8 with the latest st patch) is: = , , , , , , , ...
Parameter Value Meaning 0x10000 Device determines which of the two mode pages the device supports for selecting or deselecting compression. No Yes 1 There is one density code following in the parameter list. 0x26, 0x47, 0x48, 0x4D or 0x00 Supported density code. The value of 0x00 means use the default density chosen by the drive—which is 0x26 for DDS-4, 0x47 for DAT 72, 0x48 for DAT 160 and 0x4D for DAT 320.
Configuring an autoloader No HP autoloader media moving utilities are currently supported on Solaris. Configure the drive as described above, and then see the manual supplied with the drive for instructions on how to move media manually. What next? Once the device files have been created, you should confirm that your new tape drive is working properly. “Verifying the installation” on page 39 provides instructions on backing up and restoring a sample file to test your installation.
Sun (Solaris) servers and workstations
8 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: 1. Write test data to a tape. 2. Read the test data from the tape. 3. Compare the data read from the tape with the original data on disk. To verify the installation 1.
2. Write a sample file to tape, using 'tar': % cd / % tar cvf The options to tar have the following meanings: c Create a new archive (backup file) on the device. v Operate in verbose mode. f Specify the archive name explicitly. The arguments follow the cvf options in the command line. The arguments are as follows: The name of the archive name to be created. Example: /dev/st0 The name of the file to archive, prefixed with './' . Example: .
1. Change directory to root: % cd / 2. Back up /boot/vmlinuz to tape: % tar cvf /dev/st0 ./boot/vmlinuz 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/st0 5. Compare the original with the restored version: % cmp /boot/vmlinuz /tmp/boot/vmlinuz Note that the original filename is not prefixed with ‘.'.
Verifying the installation
9 Support and other resources HP DDS/DAT technical reference manual Related documents The following documents provide additional information: General documents and standardization • Small Computer System Interface (SCSI-1), ANSI X3.131-1986. This is the INCITS authorized standard for SCSI implementation, available through INCITS • Enhanced Small Computer System Interface (SCSI-2), ANSI X3T9.2-1993 Rev. 10L, available through INCITS • SAS1.
USB specifications • Universal Serial Bus Specification Revision 2.0 April 27, 2000 • Universal Serial Bus Mass Storage Class Specification Overview Revision 1.2 June 23, 2003 • Universal Serial Bus Mass Storage Class Specification—Mass Storage Class—Bulk Only Transport Revision 1.0 September 31, 1999 These can be obtained from: USB Implementers Forum, Inc. 5440 S.W. Westgate Drive, Suite 217 Portland, OR 97221 U.S.A. Tel: 503-296-9892 Fax: 503-297-1090 Web: www.usb.org Email: admin@usb.
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” close functionality. In Berkeley mode the tape position will remain unchanged by a device close operation. block A logical unit of information. Called “record” in the DDS-format specification.
DDS-4 uses longer tapes (150m). HP's DDS-4 drives, which are ultra-wide SCSI devices, allow transfer rates from 3 to 4 times greater than DDS-3 and capacities that are two-thirds as much again. DAT 72 tapes are 170m long and data is written in narrower tracks, again increasing data density, enabling tapes to hold 80% more data than DDS-4 tapes. DAT 160 tapes use a wider tape, which allows 120% more information to be stored than on DAT 72 tapes.
Index A AIX, 23 asynchronous data transfer, 45 AT&T mode, 45 B Berkeley mode, 45 blocks, 45 BOP, 45 buffered mode, 45 C compression, 45 D DAT, 45 DAT 72, 45 data compression, 45 data transfer, 45 DDS, 45 device files AIX, 27 IBM (AIX), 23 direct access, 46 documents, related, 43 drivers configuring for Solaris, 33 F filemarks, 46 filenames under AIX, 27 G I IBM (AIX), 23 device files, 23 immediate mode, 46 infinite flush, 46 installation, verifying, 39 L Linux servers and workstations, 29 configuring
servers HP OpenVMS, 17 Linux, 29 Solaris, 33 Sun workstations, 33 determining SCSI ID, 33 identifying attached devices, 36 synchronous data transfer, 45 systems HP-UX, 7 V verifying installation, 39 W wide data transfer, 45 workstations HP OpenVMS, 17 Linux, 29 Sun, 33 48
