Tivoli Storage Manager for HP-UX Quick Start


Using Tape Devices

Before you can use tape devices with TSM, you must do the following:

  1. Attach the devices to your system, which includes physically attaching the devices, configuring the device drivers, and determining the device names.
  2. Define the following: a library for the drives, the drives, a device class, and a storage pool associated with the device class.
  3. Include the storage pool in your storage hierarchy.

To perform these tasks you can use the administrative client command line or web interface.

This section describes the following tasks:

If you want to use a tape management system with TSM see the Administrator's Guide for details.

The examples in this section set up the following configuration:



A Closer Look

Here are some concepts that can help you to set up your tape environment (see Administrator's Guide):
Storage pool migration

To prevent disk storage pools from becoming filled with client data, you can specify that client data be automatically migrated to the tape storage pool.

A disk's high migration threshold (default value: 90%) determines when data is migrated. The low migration threshold (default value: 70%) determines when migration stops. Thus data migration from the default backup disk storage pool begins when the pool is 90% full and continues until it is at 70% full or less.

Another default is to cache data (leave the data on the storage pool) even after the data has been migrated. Cached data stays on disk for quick access until the space is needed for new data.

Scratch volumes

A scratch volume is a volume that is available for TSM use. The volume is labeled, is either blank or contains no valid data, and is not defined to TSM. You must specify the number of scratch volumes that TSM can request for this pool (MAXSCRATCH parameter).

Collocation

Collocation means that the server tries to keep a client's files on a minimal number of tape volumes. It is turned off by default. Once clients begin storing data in a storage pool with collocation off, you cannot easily change the data in the storage pool so that it is collocated. To understand the advantages and disadvantages of collocation, see the Administrator's Guide.

Attaching Devices and Installing Device Drivers

After you have physically attached a devices to the server, you must configure the appropriate device driver (add it to the kernel). The following sections discuss how this is done for drives in a manual library and for the drives and controller in an automated library.



Attaching Devices and Installing Drivers

Tape drives
You must ensure that you have configured the appropriate standard HP-UX device drivers.

Automated tape libraries
You must ensure that you have configured the SCSI pass-through device driver for the library. This driver is provided with the HP-UX operating system. The drives that are in the library are configured using the standard HP-UX device drivers.

For procedures to configure device drivers, see the documentation for the operating system.

The drivers are started when you start HP-UX. The devices must be powered on for HP-UX to recognize them.

Determining Device Names for Tivoli Storage Manager

To identify and work with removable media devices, TSM needs each device's name, the special file name.

For tape drives supported by the standard HP-UX device drivers, after you configure the device drivers, the operating system automatically assigns the special file names during system start-up. A single drive can have multiple special file names, depending on the format and recording density that the drive supports. Select the device name to use in defining the drive to TSM based on the format and density that you want TSM to use. For example, one device may have all of the following special file names:

/dev/rmt/0m
/dev/rmt/0mb
/dev/rmt/0mn
/dev/rmt/c1t0d0BEST
/dev/rmt/c1t0d0BESTb
/dev/rmt/c1t0d0BESTn
/dev/rmt/c1t0d0BESTnb

The different names represent different recording formats, densities, and operating characteristics such as data compression. For example, you might choose the name /dev/rmt/c1t0d0BEST to use the best recording format and density available on the drive.

To see these file names, you can use the HP-UX System Administration Manager (SAM), or use the ioscan command. For example, to see the device special files available for tape drives, enter the command:

+--------------------------------------------------------------------------------+
|> /usr/sbin/ioscan -fn -C tape                                                  |
+--------------------------------------------------------------------------------+

Also useful is the lssf command to get more information about a specific device special file name. See the documentation for the operating system.

For an automated tape library, the special file names for the drives in the library are created and used as described above. For the library itself, you create the special file name when you set up the SCSI pass-through driver. For example, you might create the special file /dev/tsm/library for the library. Use this special file name as the device name when defining the library to TSM.

For details about special file names, see the documentation for the operating system.

Attaching the Devices

Ensure that your devices are physically attached to your system according to the manufacturer's instructions.

Attaching Drives in a Manual Library

Here is an overview of the procedure for attaching a drive in a manual library to the server system:

  1. Install the SCSI adapter card in your system, if one is not already installed.
  2. Determine the SCSI IDs available on the SCSI adapter card to which you are attaching the device. You can use the ioscan command for this task. Find one unused SCSI ID for each drive.
  3. Follow the manufacturer's instructions to set the SCSI ID for the device to the unused SCSI ID that you found. Usually this means setting switches on the back of the device.
    Note:Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. If each device does not have a unique SCSI ID, you may have serious system problems.
  4. Follow the manufacturer's instructions to attach the device to your server system hardware.

    Attention:

    1. Power off your system before attaching a device to prevent damage to the hardware.

    2. You must attach a terminator to the last device in the chain of devices connected on one SCSI adapter card. Detailed instructions should be in the documentation that came with your hardware.
  5. Install the appropriate device driver.
  6. Determine the name for the device, which is needed to define the device to TSM. You can use SAM or the ioscan command. Select the name based on the recording format and density that you want TSM to use on this drive. See Determining Device Names for Tivoli Storage Manager.

Attaching an Autochanger and its Drives

Here is an overview of the procedure for attaching an automated library to the server system:

  1. Ensure that the SCSI adapter card is installed in your system.
    Note:Each tape autochanger that you attach for TSM use must be on its own SCSI adapter card.
  2. Determine the SCSI IDs available on the SCSI adapter card to which you are attaching the device. Find one unused SCSI ID for each drive, and one for the library or autochanger controller.
    Note:In some automated libraries, the drives and the autochanger share a single SCSI ID, but have different LUNs. For these libraries, only a single SCSI ID is required. Check the documentation for your device.
  3. Follow the manufacturer's instructions to set the SCSI ID for the drives and library controller to the unused SCSI IDs that you found. Usually this means setting switches on the back of the device.
    Note:Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. If each device does not have a unique SCSI ID, you may have serious system problems.
  4. Follow the manufacturer's instructions to attach the device to your server system hardware.

    Attention:

    1. Power off your system before attaching a device to prevent damage to the hardware.

    2. You must attach a terminator to the last device in the chain of devices connected on one SCSI adapter card. Detailed instructions should be in the documentation that came with your hardware.
  5. Ensure that you have configured the SCSI pass-through device driver for the library and the standard HP-UX driver for the drives in the library. See Configuring Device Drivers for Automated Libraries.
  6. Find the device worksheet that applies to your device. See the device configuration worksheets appendix in the Administrator's Guide.

    Record the special file names for the library and its drives on the device worksheet. The names are needed to define the library and drives to TSM.

    You created the special file names for the library and drives when you configured the SCSI pass-through driver for them. If you do not remember the names, you can use SAM or the ioscan command. See Determining Device Names for Tivoli Storage Manager.

    Keep the Worksheets:The information you record on the worksheets can help you when you need to perform operations such as adding volumes to an autochanger. Keep them for future reference.

Configuring Device Drivers for Automated Libraries
  1. Use either the SAM or the command line to manually add a SCSI pass-through driver to the kernel.
  2. Power off the system.
  3. Install and configure an autochanger to the SCSI pass-through driver.

    For more information about SCSI pass-through drivers, see scsi_pt, scsi_ctl, and autochanger in the HP-UX documentation.

    For the autochanger, use the following device file names:

    +--------------------------------------------------------------------------------+
    |/dev/rmt/xxxx     :  tape drive 1                                               |
    |/dev/rmt/xxxx     :  tape drive 2 (if the autochanger has                       |
    |                     multiple tape drives)                                      |
    |/dev/xxxx/xxxx    :  library device name                                        |
    |                     (put the file in the /dev directory)                       |
    +--------------------------------------------------------------------------------+
  4. Power on the system and the devices.
  5. After the installation and configuration are completed, check if the tape drive inside the library is supported by HP. Use the following command:
    +--------------------------------------------------------------------------------+
    |diskinfo   /dev/rmt/xxxx                                                        |
    +--------------------------------------------------------------------------------+

    If the tape drive is not supported, you will receive an I/O error message. If the tape drive is supported, you will receive the following information about the tape drive:

    +--------------------------------------------------------------------------------+
    |SCSI description of /dev/rmt/xxxxx:                                             |
    |          vendor:  HP                                                           |
    |      product id:  HPxxxxxxx                                                    |
    |            type:  sequential access                                            |
    |            size:  0 Kbytes                                                     |
    |bytes per sector:  0                                                            |
    +--------------------------------------------------------------------------------+

Setting the Library Mode

For TSM to access a SCSI library, the device must be set for the appropriate mode. The mode that TSM requires is usually called random mode; however, terminology may vary from one device to another. Two examples follow:

Refer to the documentation for your device to determine how to set it to a mode appropriate for TSM.

Adding a Manual Tape Library

In the following example, two stand-alone 8mm drives are added to Tivoli Storage Manager. Because an operator must mount tapes for these drives, you must define them as part of a manual library to TSM. You can use this example as a guide when configuring other manual tape devices. This example presents the procedure with a minimum of customization. If you want to do more, see the references in the steps for more details.

The commands, in the order entered, for defining a manual tape library are:
DEFINE LIBRARY
DEFINE DRIVE
DEFINE DEVCLASS
DEFINE STGPOOL

  1. Define a manual library and two drives associated with it. The library is named MANUALLIB. The two drives, named DRIVE01 and DRIVE02, are at SCSI adaptor 0 and SCSI IDs 1 and 2.


    Admin Command Line

    +--------------------------------------------------------------------------------+
    |define library manuallib libtype=manual                                         |
    |define drive manuallib drive01 device=/dev/rmt/1m                               |
    |define drive manuallib drive02 device=/dev/rmt/2m                               |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Server Storage.
    2. Expand Libraries and Drives.
    3. Select Manual Libraries.
    4. From Operations, select Define Manual Library.
    5. Enter the library information and Finish.
    6. Under Libraries and Drives, select Manual Drives.
    7. From Operations, select Define Manual Drive.
    8. Enter the drive information and Finish.
  2. Classify the devices by device type. It is helpful to choose a device class name that identifies the type of device for which it is intended (in this example, TAPECLASS).


    Admin Command Line

    +--------------------------------------------------------------------------------+
    |define devclass tapeclass devtype=generictape -                                 |
    |   library=manuallib                                                            |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Device Classes.
    2. Select GENERICTAPE Device Classes.
    3. From Operations, select Define Device Class.
    4. Enter the device class information and Finish.
  3. Define a storage pool named TAPEPOOL for the device class.
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |define stgpool tapepool tapeclass maxscratch=20                                 |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Server Storage.
    2. Expand Storage Pools.
    3. Select Sequential Access Storage Pools.
    4. From Operations, select Define Sequential Access Storage Pool.
    5. Enter the storage pool information and Finish.

Adding an Automated Tape Library

For the following example, an Exabyte EXB-210 library containing two drives is added to TSM. You can use this example as a guide when configuring other automated tape devices. This example presents the procedure with a minimum of customization. If you want to do more, see the references in the steps.

The commands, in the order entered, for defining an automated tape library are:
DEFINE LIBRARY
DEFINE DRIVE
DEFINE DEVCLASS
DEFINE STGPOOL

  1. Define an automated tape library and its two internal drives.

    The library is an Exabyte EXB-210, named AUTOLIB, whose SCSI library mechanism is at SCSI ID 3. The two drives, named DRIVE05 and DRIVE06, are at SCSI IDs 5 and 6. The element addresses for the drives in an EXB-210 are 82 and 83.


    Admin Command Line

    +--------------------------------------------------------------------------------+
    |define library autolib libtype=scsi device=/dev/tsm/library                     |
    |define drive autolib drive05 device=/dev/rmt/5m element=82                      |
    |define drive autolib drive06 device=/dev/rmt/6m element=83                      |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Server Storage.
    2. Expand Libraries and Drives.
    3. Select Automated Libraries.
    4. From Operations, select Define Automated Library.
    5. Enter the library information and Finish.
    6. Under Libraries and Drives, select Automated Drives.
    7. From Operations, select Define Automated Drive.
    8. Enter the drive information and Finish.


    A Closer Look

    Element address

    The element address is a number that indicates the physical location of a drive within an automated library. TSM needs the element address to connect the physical location of the drive to the drive's SCSI address. When you define a drive, the element address is required if there is more than one drive in an automated library.

  2. Classify the drives in the library by device type. It is helpful to choose a device class name that identifies the type of device for which it is intended (in this example, AUTOCLASS).


    Admin Command Line

    +--------------------------------------------------------------------------------+
    |define devclass autoclass devtype=generictape -                                 |
    |  library=autolib                                                               |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Device Classes.
    2. Select GENERICTAPE Device Classes.
    3. From Operations, select Define Device Class.
    4. Enter the device class information and Finish.
  3. Define a storage pool named AUTOPOOL for the device class.
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |define stgpool autopool autoclass maxscratch=20                                 |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Storage Pools.
    2. Select Sequential Access Storage Pools.
    3. From Operations, select Define Sequential Access Storage Pool.
    4. Enter the storage pool information and Finish.

Displaying Information About Your Devices

Before continuing, you can view the results of your definitions. If necessary, you can update these definitions by using update commands.


Admin Command Line

OR
Web Icon

Preparing Tape Volumes

All tape volumes must be labeled before TSM can use them. If you want a volume to be used only when it is requested by name, you must also define it to TSM. A defined volume is a private volume and is assigned to a specific storage pool. A volume that is not defined to TSM is a scratch volume. A storage pool can request available scratch volumes up to the number specified for that storage pool.

Preparing Tape Volumes with a Manual Drive

If you are using only one tape drive, consider labeling several tapes at this time.

  1. From an TSM administrative client command line, use a drive in the library named MANUAL to label a volume as DSM001:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |                                                                                |
    |label libvolume manual dsm001                                                   |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Server Storage.
    2. Expand Libraries and Drives.
    3. Select Library Volumes.
    4. From Operations, select Label Library Volume.
    5. Enter the volume information and Finish.
  2. Define any volumes that are to be used as private volumes. For example, define the volume you just labeled:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |                                                                                |
    |define volume tapepool dsm001                                                   |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Storage Pools.
    2. Select Sequential Access Storage Pools.
    3. Select the storage pool you want.
    4. Select Volumes.
    5. From Operations, select Define Sequential Access Volume.
    6. Enter the volume information and Finish.

Preparing Tape Volumes with an Automated Library

To label tapes with an automated library, remove any tapes that you do not want to use with TSM and load the tapes to be labeled.

  1. Use the LABEL LIBVOLUME command to label and check in the volumes. From an administrative client command line, begin a search of an automated library named AUTOLIB for unlabeled volumes and label them based on their barcodes:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |label libvolume autolib search=yes labelsource=barcode                          |
    |  checkin=scratch                                                               |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Server Storage.
    2. Expand Libraries and Drives.
    3. Select Library Volumes.
    4. From Operations, select Label Library Volume.
    5. Enter the volume information and Finish.
  2. Define any volumes that are to be used as private volumes.
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |                                                                                |
    |define volume autopool dsm001                                                   |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    1. Expand Storage Pools.
    2. Select Sequential Access Storage Pools.
    3. Select the storage pool you want.
    4. Select Volumes.
    5. From Operations, select Define Sequential Access Volume.
    6. Enter the volume information and Finish.

Including Tape in the Storage Hierarchy

You can now configure TSM so that client data can be migrated to tape. To migrate from BACKUPPOOL to AUTOPOOL and from ARCHIVEPOOL to TAPEPOOL do the following:


Admin Command Line

+--------------------------------------------------------------------------------+
|update stgpool backuppool nextstgpool=autopool                                  |
|update stgpool archivepool nextstgpool=tapepool                                 |
+--------------------------------------------------------------------------------+
OR
Web Icon
  1. Expand Server Storage.
  2. Expand Storage Pools.
  3. Select Disk Storage Pools.
  4. Select the pool to be updated.
  5. Select Update Disk Storage Pool.
  6. Enter the storage pool information and Finish.

Migrating Data from Disk to Tape

To verify that the tape devices are properly set up, migrate data from a disk storage pool. Migration requires tape mounts. The mount messages are directed to the console message queue and to any administrative client that has been started with either the mount mode or console mode option.

Trigger migration from a disk storage pool (BACKUPPOOL, for example) by setting the high and low migration thresholds to 0:
Admin Command Line

+--------------------------------------------------------------------------------+
|update stgpool backuppool highmig=0 lowmig=0                                    |
+--------------------------------------------------------------------------------+

After migration occurs, reset the thresholds to their original settings:

+--------------------------------------------------------------------------------+
|update stgpool backuppool highmig=90 lowmig=70                                  |
+--------------------------------------------------------------------------------+
OR

To migrate data from a disk storage pool and, after migration occurs, to reset the thresholds to their original settings, update the storage pool:
Web Icon

  1. Expand Server Storage.
  2. Expand Storage Pools.
  3. Select Disk Storage Pools.
  4. Select the pool to be updated.
  5. Select Update Disk Storage Pool.
  6. Enter the storage pool information and Finish.


A Closer Look

Controlling when migration occurs

Because migration from a disk to a tape storage pool uses resources such as drives and operators, you may want to control when migration occurs. To do so, leave the high migration threshold set to 100 most of the time, and lower it when you want migration to occur.

In the preceding step, you lowered both migration thresholds to 0 to verify that migration occurred. You may not want to empty the disk storage pool by setting the low migration threshold to 0 every time you want migration to occur. Normally, you may want to keep the low threshold at 40%, and vary the high threshold from as high as 90% to as low as 50%. See Administrator's Guide for details.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]