...
Step | Configuration file entry | |
|---|---|---|
| 1 | Load the SCSI device.load device | load MKXnnn |
| 2 | Link device with tape container file or
|
|
| 3 | Enable loading the virtual tape automatically. |
|
The path can point to an existing tape container file, but this is not mandatory. The emulator can create the container file if required.The parameter deviceMKXnnn encodes the device type and the device path of the emulated SCSI device presented to the guest operating system:
When loading a SCSI tape device, the parameter device has the format DDXnnn.
| Div | ||
|---|---|---|
| ||
A tape device name has the following components:
- DD: value MK; 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
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 -funfun to verify if the device has been found and the driver has been loaded. The follwoing 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.
|
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.
Multi-volume backup does 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 configured manually or 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 statusDrive: HP C1537AFormat:Status: [41114701] BOT online compression immediate-report-modeFile: 0Block: 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).
To simultate 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 hp9k Console
In some cases it may be useful to load/unload tapes manually from the hp9k console instead of using autoload. This is achieved by the following command:
Load a tape:
hp9k> deviceMKXnnn.load |
Unload a tape:
hp9k> device |
Where device 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.
| Div | ||
|---|---|---|
| ||
...