Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fix broken link

...

  • Value MK at the beginning of the device name: specifies that device type is tape.
  • X: value consists of an uppercase letter encoding the device path. Please refer to Emulated Model Hardware Configuration Details for system specific device path information.
    Example (rp4000):
    A = device path 0/0/1/0
    B = device path 0/0/1/1
    C = device path 0/0/2/0
    D = device path 0/0/2/1
  • nnn: value encodes the SCSI device connected to the SCSI controller.
    Formula: (SCSI target ID*100)+LUN
    The LUN is always 0 for tape devices.

...

Using Tapes on HP-UX Guest Systems

Displaying the Tape Configuration in HP-UX

After booting HP-UX with the virtual tape device configuration, you can use the command ioscan -C tape -fun to verify if the device was found and the driver was loaded. The following image shows an example:

The example shows two type devices and their associated special devices.

The lssf command can be used to verify that the special files point to the correct device paths, SCSI target ID and LUN.

# lssf /dev/rmt/0m

stape card instance 0 SCSI target 5 SCSI LUN 0 at&t best density
available at address 0/0/1/0.5.0 /dev/rmt/0m

Loading and Ejecting the Virtual Tape in HP-UX

Using the autoload Configuration Option 

If autoload has been enabled in the configuration, the virtual tape is "loaded" and the container file created, if required, when the tape device is accessed.

Please note: Multi-volume backup software may not work correctly when autoload is enabled. If a new tape is requested by the software, it will not wait for a new tape to load but overwrite the existing file. If data is to be written to several tapes, this needs to be implemented manually (e.g., by a customized script).

For example, the following command will cause the container file for device /dev/rmt/0mnb (default tape device) to be created and opened:

# mt status
Drive: HP C1537A
Format:
Status: [41114701] BOT online compression immediate-report-mode
File: 0
Block: 0

The tape can be "ejected" by setting it to offline (device-name is the full path to the special file):

# mt -f <device-name> offl

After the offline command, the container file can be removed (i.e., the tape can be archived).

Div
classpagebreak



To simulate the "swapping" of tapes, use the sequence:

  • Release a loaded tape so its container file can be moved away: mt -f <devicename> offl
  • Write to the tape as required (this will create a new container file, if needed).
  • Release the loaded tape so its container file can be moved away: mt -f <devicename> offl

Using Manual Tape Loading from the PA9 Console

In some cases it may be useful to load/unload tapes manually from the pa9-64 or pa9-32 console instead of using autoload. This is achieved by the following command (using PA9-64 as an example):

Load a tape:

pa9-64> MKXnnn.load 

Unload a tape:

pa9-64> MKXnnn.unload

Where MKXnnn stands for the virtual tape configuration name, for example, MKA500.

If no tape is "loaded" in the virtual tape device, the command

mt -f <device-name> status

will show a status of 0.

Reading and Writing Tapes in HP-UX

There are several commands that can be used to write data to / read data from the virtual tapes, for example,

  • tar
  • fbackup/frecover
  • dump/restore
  • vxdump/vxrestore

Please refer to your HP-UX documentation for details about the usage of these utilities.

Divclasspagebreak


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc