HP 157770-001 - DAT Drive 20/40 Tape User manual

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
Part number: DW049-90915
Edition 1: May 2009
30 Mar 07

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.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided
“as is” without warranty of any kind and 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.
Changes in this edition
• Addition of HP DAT 320 USB drive.
HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 3
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General documents and standardization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
USB specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
SAS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Drivers and backup software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
UNIX applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Application software availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Inquiry Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 HP (HP-UX) servers and workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Determining a suitable SCSI ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Adding stape and schgr (autoloader driver) to the kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Add device files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring an autoloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
What next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 HP (OpenVMS) servers and workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Determining attached devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring an autoloader on OpenVMS and MRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Verifying the configuration of an autoloader on OpenVMS and MRU . . . . . . . . . . . . . . . . . . . . . 20
What next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 HP (Tru64 5.1x) servers and workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Updating the tape driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring an autoloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
What next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5 IBM (AIX) servers and workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Determining the SCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring the device files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
If you are using a graphics terminal running X-Windows . . . . . . . . . . . . . . . . . . . . . . . . . 25
If you are using a non-graphics terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Device filenames under AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6 Linux (kernel 2.6.x) servers and workstations . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Determining the SCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuring on Linux systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Contents

4
Using the seek and tell features of mt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring non-compression device files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Detecting autoloader LUNs in Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing USB drivers on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Verifying an autoloader has installed correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
What next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7 Sun (Solaris) servers and workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Determining the SCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Driver configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
HP-data values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring an autoloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
What next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8 Verifying the installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
To verify the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 5
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. The information is given
in good faith, but since the operating systems and any upgrades that are made to them are outside
Hewlett-Packard’s control, HP cannot guarantee that the details are correct. Please consult the
operating system documentation in conjunction with this guide.
This guide provides basic information on configuring the following drives with various operating
systems:
•HP DDS-4 drive, USB and SCSI, capacity 40 GB
•HP DAT 72 drive, USB, SCSI and SAS, capacity 72 GB
•HP DAT 72 autoloader, SCSI, capacity 720 (10x72) GB
•HP DAT 160 drive, USB, SCSI and SAS, capacity 160 GB
•HP DAT 320 drive, USB, capacity 320 GB
The capacities use hardware data compression with a compression ratio of 2:1.
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
•DDS-4
ECMA-288
•DAT 72
3.81 mm Wide Magnetic Tape Cartridge for Information Exchange - Helical Scan Recording
DAT 72 Format using 170m Length Tapes — controlled HP document
•DAT 160
DDS Generation 6 Format Standard — HP internal document A-5969-3055-1
•DAT 320
DDS Generation 7 Format Standard — HP internal document A-5969-3070-1

6
Copies of General Documents can be obtained from:
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: [phone]
Fax: [phone]
Web: www.usb.org
Email: [e-mail]
SAS compliance
SAS drives are compliant to:
•SAM2 ANSI INCITS.366:2003
•SAS1.1 ANSI INCITS.417:2006
•SPC2 ANSI INCITS.351:2001
•SSC2 ANSI INCITS.380:2003
INCITS 11 West 42nd Street, New York, NY 10036-8002, USA
ISO CP 56, CH-1211 Geneva 20, Switzerland
ECMA 114 Rue du Rhône, CH-1204 Geneva, Switzerland
Tel: [phone]
Web URL: http://.www.ecma.ch
Global Engineering
Documents
2805 McGaw, Irvine, CA 92714, USA
Tel: [phone] or 714 261 1455

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 7
1Introduction
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
cpio and tar. To achieve more sophisticated control of the drives, and to exploit the full range of
DDS features, it is worth considering software applications specifically designed for the task.
Application software availability
Most backup software companies provide applications for HP DDS/DAT products. Contact your
software supplier for details. Alternatively, contact your HP supplier, who can provide you with
details of a wide range of compatible software.
For details of software for autoloaders, please contact your support center.
Inquiry Strings
Most backup applications identify HP DDS/DAT products by their inquiry strings. The inquiry strings
for the products are shown in the following table:
Product Inquiry String
HP DDS-4 drive C5683A
HP DAT 72 drive C7438A
HP DAT 72 autoloader DAT72X10
HP DAT 160 drive DAT160
HP DAT 320 drive DAT320

Introduction8

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 9
2 HP (HP-UX) servers and workstations
This chapter covers:
•HP servers and workstations: HP-UX 11i v1 (11.11), 11i v2 (11.23)
•HP servers: HP-UX 11i v3 (11.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. This ensures that you will
have the correct device driver for your tape drive.
System Administration Management (SAM) tools have evolved with ongoing HP-UX version releases.
As a result, the procedures for setting up with different HP-UX versions differ. They are described
separately in this chapter.
HP-UX11i v3 and agile addressing
HP-UX11i v3 introduces agile addressing of devices. Agile addressing uses a different format of the
device special file (dsf) to represent the tape drive—known as a persistent dsf. However HP-UX11i v3
retains support for the legacy dsf format as used in HP-UX11i v1 and 11i v2.
For more information about HP-UX releases including HP-UX11i v3 please refer to
www.docs.hp.com.
Determining a suitable SCSI ID
The tape drive SCSI ID setting must be unique for the SCSI bus to which the drive is attached. Often
the drive will be the only device on the bus1in which case the default SCSI ID of 3 is suitable. See
the drive’s User Guide for details of how to physically alter the SCSI ID setting (usually accessible at
the rear panel of the drive).
Scan the system to list the existing devices attached. From a shell window (hpterm/xterm), execute
ioscan as shown below:
For HP-UX 11i v1, 11i v2 and 11i v3 (legacy format)
%/sbin/ioscan –f
The output should look similar to the following:
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (880)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
1. Note that HP does not support disk drives and tape drives sharing the same SCSI bus.

HP (HP-UX) servers and workstations10
OO 0 0/0/1/0 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035)
OO 1 0/0/1/1 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035)
OO 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
: : : : : : :
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ext_bus 6 0/3/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60001
ext_bus 7 0/3/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60001
target 1 0/3/1/1.3 tgt CLAIMED DEVICE
tape 1 0/3/1/1.3.0 stape CLAIMED DEVICE HP DAT160
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 5 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
: : : : : : :
processor 1 129 processor CLAIMED PROCESSOR Processor
For a particular SCSI device in the ioscan listing, you can decode the SCSI bus ID and the drive’s
SCSI ID and LUN ID from the H/W path (hardware path). For example:
Class I H/W Path Driver S/W State H/W Type Description
tape 1 0/3/1/1.3.0 stape CLAIMED DEVICE HP DAT160
•The H/W path for the tape drive is “0/3/1/1.3.0”.
•SCSI bus ID is “0/3/1/1” (including all the numbers separated by “/”).
From the remaining “.3.0” portion:
•Tape drive SCSI ID = 3
•Tape drive SCSI LUN = 0
For 11i v3 (Agile i/O Tree view)
Enter the command:
%ioscan -m lun
The output should look similar to the following1
Class I Lun H/W Path Driver S/W State H/W Type Health Description
============================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE online HP 73.4GST373454LC
0/1/1/0.0x0.0x0
/dev/disk/disk2 /dev/rdisk/disk2
disk 3 64000/0xfa00/0x3 esdisk CLAIMED DEVICE online TEAC DV-28E-N
0/0/2/0.0.0x0.0x0
/dev/disk/disk3 /dev/rdisk/disk3
tape 5 64000/0xfa00/0xa estape CLAIMED DEVICE online HP DLT VS160
0/2/1/1.0x5.0x0
/dev/rtape/tape5_BEST /dev/rtape/tape5_BESTb /dev/rtape/tape5_BESTn
/dev/rtape/tape5_BESTnb
tape 9 64000/0xfa00/0x12 estape CLAIMED DEVICE online HP C5683A
0/1/1/1.0x2.0x0
/dev/rtape/tape9_BEST /dev/rtape/tape9_BESTb /dev/rtape/tape9_BESTn
/dev/rtape/tape9_BESTnb
tape 0 64000/0xfa00/0x16 estape CLAIMED DEVICE online HP DAT160
0/3/1/1.0x3.0x0
1. Device files (such as /dev/rtape/tape9_BEST) may or may not be in place initially.

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 11
/dev/rtape/tape0_BEST /dev/rtape/tape0_BESTb /dev/rtape/tape0_BESTn
/dev/rtape/tape0_BESTnb
tape 12 64000/0xfa00/0x1a estape CLAIMED DEVICE online HP 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 I Lun H/W Path Driver S/W State H/W Type Health Description
tape 0 64000/0xfa00/0x16 estape CLAIMED DEVICE online HP DAT160
0/3/1/1.0x3.0x0
The lunpath hardware path for the tape drive is “0/3/1/1.0x3.0x0”.
•SCSI bus ID is “0/3/1/1” (including all the numbers separated by “/”).
From the remaining “0x3.0x0” portion:
•Tape drive SCSI ID = 3 (decimal value from 0x3)
•Tape drive SCSI LUN = 0 (decimal value from 0x0)
Adding stape and schgr (autoloader driver) to the kernel
For HP-UX 11i v1, 11i v2
If your tape drive or autoloader does not appear in the ioscan listing or is listed with H/W Type
“UNKNOWN” you may need to install the appropriate drivers.

HP (HP-UX) servers and workstations12
Use the ‘sam’ 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.
Figure 1 SAM GUI
Figure 2 SAM text-based interface
For HP-UX 11i v1 (HP-UX 11.11)
1. Enter sam at the command line.
%sam
2. Select the following:

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 13
Kernel Configuration
Drivers
3. Highlight the stape driver. If the driver has not been added to the kernel, both Current State and
Pending State will read “Out”.
4. Select the following:
Actions
Add Driver to Kernel
The Pending State will now read “In”.
5. To add the new driver to the kernel, select:
Actions
Create a New Kernel
The stape or schgr driver is added to the kernel.
6. If you are going to attach an autoloader, use a similar procedure to change schgr to “static”.
7. Reboot the system.
For HP-UX 11i v2 (HP-UX 11. 23 )
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. If you are going to attach an autoloader, use a similar procedure to change schgr to “static”.
6. The stape and schgr drivers are now added to the kernel.
7. Reboot the system.
For HP-UX 11i v3 (HP-UX 11.31)
1. Start up the SMH web-based interface.
% smh –w
This will attempt to launch a web browser. Mozilla browser1is the default when HP-UX 11i v3 is
installed.
1. If Mozilla is being invoked for the first time you may be asked to agree to license terms for the software.

HP (HP-UX) servers and workstations14
2. From the SMH Tools page (see Figure 3), 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 module1radio button. Its details will appear in a panel below the modules
list. From the right hand panel on the web page, click the Modify Module link.
1. T h e estape and stape modules are linked, so it is sufficient to select the estape module alone for installation.

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 15
5. 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 4).
Figure 4 Adding estape driver to the kernel
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 autoloaders, 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.
10. Following the reboot ,re-run SMH and search again for the driver as in step 3 above. Current
State and Next Boot State should both be listed as “static”.
Add device files
For HP-UX 11i v1, 11i v2
Use the sam utility to create device files. sam runs as a mouse driven GUI (see Figure 1 on page 12)
on a system with full graphics capability, or as a console text-based interface (see Figure 2 on page
12). If you use the text-based interface, use the Tab and arrow keys to navigate, and the Return key
to select.
1. Enter sam at the command line.
% sam
2. Select the following:
Peripheral Devices
Tape Drives
sam will then scan the system for any tape drives connected.

HP (HP-UX) servers and workstations16
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
3. 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. To view the device files that have been created,
select:
Actions
Create Device Files
Show Device Files
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 for most applications:
cXtYdZBESTnb = Berkeley, no rewind, best available density
cXtYdZBESTb = Berkeley, with rewind, best available density
where:
X= card number
Y= target number (drive SCSI ID)
Z= LUN number
For HP-UX 11i v3 (HP-UX 11.31)
1. Start up the SMH web-based interface:
%smh –w
This will attempt to launch a web browser. Mozilla browser1is the default when HP-UX 11i v3 is
installed.
2. From the SMH Tools page (see Figure 3 on page 14), select Manage Peripheral Devices from the
Peripheral Devices section.
1. If Mozilla is being invoked for the first time you may be asked to agree to license terms for the software.

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 17
3. Select tape from the Class drop down box on the HP-UX Peripheral Device Tool page. Select the
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 5)1
.
Figure 5 Selecting a tape device to create its device files (Agile View)
4. From the right-hand panel on the HP-UX Peripheral Device Tool page, click on Reinstall Device
Files. At the next page, click the Reinstall button. When the browser returns to the HP-UX
Peripheral Device Tool page, click the Refresh button one or more times until the list of device
files appears under the Properties header.
Configuring an autoloader
1. Reboot the system with the autoloader attached.
2. Run ioscan -funC autoch to find the device files for the autoloader.
If there are no device files listed, proceed as follows:
3. Create /dev/rac if it does not exist.
4. Run ioscan -funC tape to find the tape device file.
5. Execute: ls -al /dev/rmt/<device_file>
This will return an output similar to:
2 bin bin 205 0x0450c0
This example tells you that the card number is 4 and the target number 5.
6. Run mknod to create the device files:
mknod /dev/rac/c<X>t<Y>d<Z> c 203 0x0<X><Y><Z>00
where:
<X> is the card number
<Y> is the target number
<Z> is the LUN
1. Depending on how SMH was last used the HP-UX Peripheral Device Tool page will display either the Agile View or the
Legacy View as referenced in the Introduction to this chapter (page 9). To switch between these views use the Toggle
Global Device View link on the right hand side of the HP-UX Peripheral Device Tool page. In this chapter, the Agile View
is assumed. The process is similar for the Legacy View.

HP (HP-UX) servers and workstations18
For example, using values from the ls -al output above and a LUN of 1, you would execute:
mknod /dev/rac/c4t5d1 c 203 0x045100
To verify that the autoloader has installed correctly, run the following mc 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. For more details of the mc command, run
man mc.
What next?
Once the device files have been created, you should confirm that your new tape drive is working
properly. Chapter 8, “Verifying the installation” provides instructions on backing up and restoring a
sample file to test your installation.

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 19
3 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 Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
MKA400: Online 0
use this value in the next command line
$ sho dev MKA400/full
Magtape MKA400:, device type HP C7438A, is online, record-oriented
device, file-oriented device, available to cluster, error logging
is enabled, controller supports compaction (compaction disabled),
device supports fastskip (per_io).
Error count 0 Operations completed 222530
Owner process "" Owner UIC [1,4]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer size 512
Density default Format Normal-11
Volume status: no-unload on dismount, beginning-of-tape, odd parity.
Configuring an autoloader on OpenVMS and MRU
1. Find the name of the changer device by executing:
$ mcr sysman io auto/log
If the DAT tape drive is at device ID mka400, the changer device will be gka401.
The parts of the device name are as follows:
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.
gk SCSI changer
aFirst SCSI bus
4SCSI target ID 4
01 LUN 01

HP (OpenVMS) servers and workstations20
Verifying the configuration of an autoloader on OpenVMS and
MRU
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: 10
Drives: 1
Inports: 0
Outports: 0
Transports: 1
For further details on MRU and using the robot commands, see the MRU User Guide.
What next?
Once device files have been created, you should confirm that your new tape drive is working
properly. Chapter 8 on page 37 provides instructions on backing up and restoring a sample file to
test your installation.