Quick Start


Using Tape and Optical Devices with Tivoli Storage Manager

Before you can use tape and optical 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:



Figure AB0CT107 not displayed.

If TSM will use a tape library controlled by the Storage Tek Automated Cartridge System Library Software, you must set the CSI_HOSTNAME in the /opt/tivoli/tsm/devices/bin/rc.acs_ssi file. Define the environment variable ACSLS_SERVER_HOSTNAME in the /etc/environment or /etc/profile. You do not need to reset the variable at the next product update.


Figure AB0CT108 not displayed.

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

For TSM to use a device, you must physically attach the devices to the server and install the appropriate device driver on your system. The following sections discuss how this is done for drives in a manual library and for the drives and controller in automated libraries.



Attaching Devices and Installing Drivers

IBM tape drives, tape autochangers, and tape libraries
Install the IBMtape device driver. For an IBM 3494, install the IBM Tape Library Driver for Sun Solaris, which includes the lmcp daemon. See Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives, Installing Device Drivers for IBM 349X Libraries, and IBM SCSI Device Drivers: Installation and User's Guide.

Non-IBM tape drives and tape autochangers
Install the TSM device drivers. When you install TSM, you must choose whether to install the TSM device drivers for tape and tape autochanger devices. See Installing Device Drivers for how to install the device drivers.

Optical devices
Install the TSM device drivers.

The drivers are started when you start AIX. The devices must be powered on for AIX recognize them.

Determining Device Names for Tivoli Storage Manager

To identify and work with removable media devices, TSM needs the device's special file name. When a device configures successfully, a logical file name is returned in the form of opx, mtx, or lbx, where x is a numerical value that indicates the instance of a device for a particular class.

During configuration, a device special file name is created as one of the following. In this table, x denotes any integer of 0-9:

Special File Name Description
/dev/mtx Used by all tape drives that are not supported by IBM hardware device drivers
/dev/lbx Used by most TSM-supported SCSI libraries
/dev/ropx Used by all TSM-supported optical drives
/dev/rmtx Used by the GENERICTAPE device type
/dev/smcx Used by 3570 and 3575 libraries, and used to define the Automatic Cartridge Facility feature of the IBM 3590 B11 as a library
/dev/lmcpx Used by 349X automatic tape libraries

The following are examples of special file names:

Table 3. Examples of Device Special File Names

If the logical file name is: The device special file name is:
mt3 /dev/mt3
lb0 /dev/lb0
1op /dev/r1op
rmt1 Drive: /dev/rmt1

Medium changer: /dev/rmt1.smc (3590 B11 ACF, 3570, and 3575)

rmt2 /dev/rmt2
lmcp0 /dev/lmcp0
Note:You must know the device special file name when you use the DEFINE DRIVE or DEFINE LIBRARY commands. The special file name is the value that you specify with the DEVICE= parameter. You can use the SMIT tool to get the device special file.

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. 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. See Determining Device Names for Tivoli Storage Manager.

Attaching an Autochanger and its Drives

  1. Install the SCSI adapter card in your system, if not already installed.

  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. Install the appropriate device drivers. See Attaching Devices and Installing Device Drivers.

  6. Find the device worksheet that applies to your device.

  7. Determine the name for the device, which is needed to define the device to TSM, and record the name on the device worksheet.

    The device name for each drive has the form /dev/mtx. The device name for the library controller has the form /dev/lbx. In both cases, x is the number assigned when the drive and library was set up with its device driver.

    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.

Installing Device Drivers

This section describes how to install the available device drivers.

Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives

For IBM 3490, 3570, and 3590 devices, see IBM SCSI Device Drivers: Installation and User's Guide for how to install the device drivers.

After completing the procedure in the manual, you receive a message from the system:

Installing Device Drivers for IBM 349X Libraries

For an IBM 3494 or 3495 Tape Library Dataserver, refer to either the IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers or the IBM AIX Parallel and ESCON Channel Tape Attachment/6000 Installation and User's Guide.

After completing the procedure in the manual, you will receive a message (logical filename) of the form:

+--------------------------------------------------------------------------------+
|lmcpx Available                                                                 |
+--------------------------------------------------------------------------------+

where x is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.

For example, if the message is lmcp0 Available, enter /dev/lmcp0 on the worksheet in the Device Name field for the library. Always use the /dev/ prefix with the name provided by the system.

Configuring an Autochanger or a Robot Device Driver for a Library
Note:Use the procedure in this section to configure autochangers and robot device drivers excluding IBM 3494 and IBM 3495.

The term Robot is defined as a device that performs programmed operations or that operates by remote control.

Run the SMIT program to configure the device driver for each autochanger or robot:

  1. Select Devices.

  2. Select TSM Devices.

  3. Select Library/MediumChanger.

  4. Select Add a Library/MediumChanger.

  5. Select the TSM-SCSI-LB for any TSM supported library.

  6. Select the parent adapter to which you are connecting the device. This number is listed in the form: 00-0X, where X is the slot number location of the SCSI adapter card.

  7. When prompted, enter the CONNECTION address of the device you are installing. The connection address is a two-digit number. The first digit is the SCSI ID (the value you recorded on the worksheet). The second digit is the device's SCSI logical unit number (LUN), which is usually zero, unless otherwise noted.

    For example, a connection address of 40 has a SCSI ID=4 and a LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.

  8. Click on the DO button.

    You will receive a message (logical filename) of the form lbX Available. Note the value of X, which is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.

    For example, if the message is lb0 Available, the Device Name field is /dev/lb0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.

Configuring Tape Drives for Use by AIX

Tape drives cannot be shared when TSM is started. They can only be shared when the drive is not defined to TSM, or TSM is not started.

Note:The mksysb command does not work if both TSM and AIX are sharing the same drive or drives.

To use the operating system's native tape device driver in conjunction with a SCSI drive, the device must be configured to AIX first and then configured to TSM. These steps cannot be done in reverse order. Configure the device to AIX through the following choices from SMIT:

+--------------------------------------------------------------------------------+
|   Select Devices                                                               |
|      Select Tape Drive                                                         |
|         Select Add A Tape Drive                                                |
+--------------------------------------------------------------------------------+

To define the devices to TSM, go to Configuring a Device Driver for a Tape or an Optical Drive.

Configuring a Device Driver for a Tape or an Optical Drive

Notes:

  1. Use the procedure in this section to configure TSM device drivers for tape or optical drives excluding IBM 3490, 3570, and 3590. See Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives.

  2. TSM cannot write over tar or dd tapes, but tar or dd can write over TSM tapes.

Run the SMIT program to configure the device driver for each drive (including drives in libraries) as follows:

  1. Select Devices.

  2. Select TSM Devices.

  3. Select Tape Drive or Optical R/W Disk Drive, depending on whether the drive is tape or optical.

  4. Select Add a Tape Drive or Add an Optical Disk Drive, depending on whether the drive is tape or optical.

  5. Select the TSM-SCSI-MT for any TSM supported tape drive or TSM-SCSI-OP for any TSM supported optical drive.

  6. Select the adapter to which you are connecting the device. This number is listed in the form: 00-0X, where X is the slot number location of the SCSI adapter card.

  7. When prompted, enter the CONNECTION address of the device you are installing. The connection address is a two-digit number. The first digit is the SCSI ID (the value you recorded on the worksheet). The second digit is the device's SCSI logical unit number (LUN), which is usually zero, unless otherwise noted.

    For example, a connection address of 40 has a SCSI ID=4 and LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.

  8. Click on the DO button.

    The message you receive next depends on whether you are configuring the device driver for a tape or an optical device:

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 and optical 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 DRIVE1 and DRIVE2, are at SCSI adaptor 0 and SCSI IDs 1 and 2.



    Figure AB0CT124 not displayed.

    define library manuallib libtype=manual
    
    define drive manuallib drive1 device=/dev/mt1
    
    define drive manuallib drive2 device=/dev/mt2
    



    Figure AB0CT338 not displayed.

    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).



    Figure AB0CT124 not displayed.

    define devclass tapeclass devtype=8mm -
      format=8500 library=manuallib
    



    Figure AB0CT338 not displayed.

    1. Expand Device Classes.

    2. Select 8MM 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.



    Figure AB0CT124 not displayed.

    define stgpool tapepool tapeclass maxscratch=20
    



    Figure AB0CT338 not displayed.

    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.

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 DRIVE5 and DRIVE6, are at SCSI IDs 5 and 6. The element addresses for the drives in an EXB-210 are 82 and 83.



    Figure AB0CT124 not displayed.

    define library autolib libtype=scsi device=/dev/lb3
    
    define drive autolib drive5 device=/dev/mt5 element=82
    
    define drive autolib drive6 device=/dev/mt6 element=83
    



    Figure AB0CT338 not displayed.

    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.



    Figure AB0CT108 not displayed.

    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).



    Figure AB0CT124 not displayed.

    define devclass autoclass devtype=8mm -
     format=8500 library=autolib
    



    Figure AB0CT338 not displayed.

    1. Expand Device Classes.

    2. Select 8MM 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.



    Figure AB0CT124 not displayed.

    define stgpool autopool autoclass maxscratch=20
    



    Figure AB0CT338 not displayed.

    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.


Figure AB0CT124 not displayed.

  • To query the libraries:
       query library
    

  • To query the drives:
       query drive
    

  • To query the device classes:
       query devclass format=detailed
    

  • To query the storage pools:
       query stgpool
    



Figure AB0CT338 not displayed.

  • To query the libraries and drives:

    1. Expand Libraries and Drives.

    2. Select:

      • Manual Libraries or Automated Libraries and then the libraries you have defined

      • Manual Drives or Automated Drives and then the drives you have defined

  • To query the device classes:

    1. Expand Device Classes.

    2. Select 8MM Device Classes and then the device classes you have defined.

  • To query the storage pools:

    1. Expand Storage Pools.

    2. Select Sequential Access Storage Pools and then the storage pools you have defined.

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:

    Figure AB0CT124 not displayed.

    label libvolume manual dsm001
    



    Figure AB0CT338 not displayed.

    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:

    Figure AB0CT124 not displayed.

    define volume tapepool dsm001
    



    Figure AB0CT338 not displayed.

    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:

    Figure AB0CT124 not displayed.

    label libvolume autolib search=yes labelsource=barcode
      checkin=scratch
    



    Figure AB0CT338 not displayed.

    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.

    Figure AB0CT124 not displayed.

    define volume autopool dsm001
    



    Figure AB0CT338 not displayed.

    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:


Figure AB0CT124 not displayed.

update stgpool backuppool nextstgpool=autopool
update stgpool archivepool nextstgpool=tapepool



Figure AB0CT338 not displayed.

  1. Expand Storage Pools.

  2. Select Sequential Access Storage Pools.

  3. Select the pool to be updated.

  4. Select Update Sequential Access Storage Pool.

  5. Enter the storage pool information and Finish.

Migrating Data from Disk to Tape

To verify that the tape devices is 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.


Figure AB0CT124 not displayed.

Trigger migration from a disk storage pool (BACKUPPOOL, for example) by setting the high and low migration thresholds to 0:
update stgpool backuppool highmig=0 lowmig=0

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

update stgpool backuppool highmig=90 lowmig=70


Figure AB0CT338 not displayed.

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

  1. Expand Storage Pools.

  2. Select Sequential Access Storage Pools.

  3. Select the pool to be updated.

  4. Select Update Sequential Access Storage Pool.

  5. Enter the storage pool information and Finish.


Figure AB0CT108 not displayed.

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 ]