...
Table of Contents |
---|
exclude | Table of contents |
---|
style | square |
---|
|
Adding Tape Devices to the Configuration File
...
1 | Load the SCSI device. | load MKXnnn |
2 | Link the device with tape container file or
physical tape device | MK Xnnn .image="/path/to/tape-container-file"
The path can point to an existing tape container file, but this is not mandatory. The emulator can create the container file if required.
MK Xnnn .image="/dev/stN"
 You can identify the Linux tape device name using the command dmesg |grep -i tape . N stands for the device number, e.g., /dev/st0.
|
3 | Enable loading the virtual tape automatically (for virtual tapes based on container file). | MK Xnnn .autoload=yes
Multi-volume backup software may not work correctly when autoload is enabled. If a new tape is requested by the software, it may not wait for a new tape to load but overwrite the existing file. If data is must be written to several tapes, this needs to be implemented manually, e.g., by a customized script.
Without autoload enabled, MPE/iX can load a tape using the DEVCTRL command. There is no such option for HP-UX guest systems. The autoload command can help to overcome this deficiency. Please note the note above!
|
...
The parameter MKXnnn encodes the device type and the device path of the emulated SCSI device presented to the guest operating system:
...