Setup Tape Libraries and Drives

** Credit Web

Setup Tape Libraries and Drives

1. IBM 3584

If using an IBM 3584 tape library, install the Atape driver, configure the SCSI Medium Changer (SMC) library device on the node that will run the HPSS LTO PVR, and verify that you can talk to the library.

To install the Atape driver use smitty in AIX:

% smitty install

To configure the library:

root% cfgmgr

root% lsdev -Cc tape | grep smc

smc0 Available 40-58-00-0,1 IBM 3584 Library Medium Changer

To test communications with the library:

% tapeutil -f inventory

To test tape mounts:

% tapeutil -f move

To test tape dismounts:

% tapeutil -f unload

% tapeutil -f move

Run this before HPSS has started since only one process can have an open smc device file descriptor.

For drives in an IBM 3584 robot, identify the robot-specific device id (LTO drive locations) for each Mover tape device. This will be required when configuring the tape drives within HPSS.

To identify robot-specific device ids for each Mover tape device in an LTO robot:

% tapeutil -f inventory

Look for addresses of drive devices in the output.

Refer to 6.8.13.2 LTO PVR Information for more information.

2. 3494

For a 3494 tape library:

• Identify the robot-specific device id for each Mover tape device. This will be required when configuring the tape drives within HPSS.

To identify robot-specific device id for each Mover tape device in a 3494 robot:

% /opt/hpss/bin/GetESANumbers

• Identify range(s) of tape cartridge labels to be used by HPSS.

• Configure the lmcp daemon on the node that will run the HPSS 3494 PVR, verify that it is working properly, and configure the lmcp daemon to be started automatically during system reboot.

To see if lmcp daemon is running:

% ps -e | grep lmcpd

To start the lmcp daemon:

root% /etc/methods/startatl

To test whether lmcp daemon is configured and working correctly:

% mtlib -l -qL

where lmcpDevice is usually /dev/lmcp0 .

To test ability to use lmcp daemon to mount a tape:

% mtlib -l/dev/lmcp0 -m -V -x

Test ability to dismount the tape:

% mtlib -l/dev/lmcp0 -d -V -x

To automatically start the lmcp daemon after system reboot, add /etc/methods/startatl to the /etc/inittab file

Refer to 6.8.13.3 IBM 3494/3495 PVR Information for more information.

3. STK

For an STK tape library:

• If using an STK tape library, configure the ACSLS and SSI software properly and verify that it is working correctly.

To test the ability to mount and dismount a tape in an STK library, use the stk_ctl utility that is provided by the HPSS automated SFS backup toolset.

To mount a tape:

% stk_ctl mount

where driveSpec is four integers separated by commas (no spaces), identifying the ACS, LSM, panel, and drive (e.g., 0,0,1,2 ).

To dismount a tape:

% stk_ctl dismount

To query a drive:

% stk_ctl query

Refer to 6.8.13.4 StorageTek PVR and RAIT PVR Information for more information.

4. AML

For AML tape libraries:

• If using an AML PVR, configure the Insert/Eject ports using the configuration files /var/hpss/etc/AML_EjectPort.conf and /var/hpss/etc/AML_InsertPort.conf .

Refer to 6.8.13.5 ADIC Automatic Media Library Storage Systems Information for more information.

5. Tape Drive Verification

Verify that the correct number and type of tape devices are available on each Tape Mover node.

5.1 AIX

The tape devices section of the lsnode report displays all available tape drives.

To manually find out the type and number of available tape devices:

% lsdev -C -S a -c tape

• On each Tape Mover node, verify that each tape drive has variable-length block size set.

The tape devices section of the lsnode report indicates whether the available tape drives have variable-length block size set.

To manually check whether variable block size is enabled, the following should return a value of zero( 0 ):

% lsattr -E -l -a block_size -F value

To change the device to use variable block size:

root% chdev -l -a block_size=0

• If using STK drives (e.g., Redwoods), verify that the drive type is not incorrectly set to Generic tape drive or IBM Emulation mode.

• On each Tape Mover node, verify that the raw read and write I/O performance of all HPSS tape drives are at expected levels. Create one or more tables documenting the results. An example table can be found above.

To measure uncompressed write performance (see warning below) on rmt1 (Note that specifying rmt1.1 causes the tape not to rewind):

% iocheck -w -t 20 -b 1mb /dev/rmt1.1

To measure the maximum-compressed write performance on rmt1 (and then rewind the tape):

% iocheck -w -t 20 -f 0 -b 1mb /dev/rmt1

To measure read performance on drive rmt1 using the previously-written uncompressed and compressed files:

% iocheck -r -t 20 -b 1mb /dev/rmt1.1

% iocheck -r -t 20 -b 1mb /dev/rmt1.1

WARNING: The contents of this tape will be overwritten so be sure to mount the correct tape cartridge.

To unload a tape:

% tctl -f rewoffl

Repeat the above steps for each tape drive.

5.2 Solaris & IRIX

For Solaris & IRIX platforms, specific commands and syntax are not listed. Perform the following steps using the appropriate commands for the OS used:

• On each Tape Mover node, verify that each tape drive has variable-length block size set.

• If using STK drives (e.g., Redwoods), verify that the drive type is not incorrectly set to Generic tape drive or IBM Emulation mode.

• On each Tape Mover node, verify that the raw read and write I/O performance of all HPSS tape drives are at expected levels. Create one or more tables documenting the results. An example table can be found above.