Tivoli Header

Quick Start


Using Tape Devices and Optical Devices

Before you can use tape and optical devices with Tivoli Storage Manager, 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 Tivoli Storage Manager see the Administrator's Guide for details.

The examples in this section set up the following configuration:



Attention

If Tivoli Storage Manager 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.


A Closer Look Symbol

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 the server to use. The volume is labeled, is either blank or contains no valid data, and is not defined to Tivoli Storage Manager. You must specify the number of scratch volumes that the server 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 Tivoli Storage Manager 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 and autochangers
Install the device driver that IBM supplies. See Installing Device Drivers for IBM SCSI Tape Drives, Installing Device Drivers for IBM 349X Libraries, and IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide.

Non-IBM tape drives and autochangers
You must ensure that you have installed the appropriate device drivers. When you install Tivoli Storage Manager, you must choose whether to install the Tivoli Storage Manager device driver or the native operating system device driver for tape devices.

Optical devices
Install the TSM device drivers. See http://www.tivoli.com/support/storage_mgr/tivolimain.html and Configuring Device Drivers for Non-IBM Tape or Optical Drives.

Selecting Device Drivers

Table 9 and Table 10 list the device drivers needed for Tivoli Storage Manager drives and libraries.

Table 9. Device Drivers for Tape and Optical Drives

Device Device Type Library Type Device Driver
4MM drive 4MM External, Manual, SCSI Tivoli Storage Manager device driver
8MM drive 8MM External, Manual, SCSI
DLT drive DLT External, Manual, SCSI
DTF drive DTF External, Manual, SCSI
QIC drive QIC External, Manual, SCSI
STK SD3, 9490, 9840, 9940 drive ECARTRIDGE External, Manual, SCSI, ACSLS
Optical drive OPTICAL External, Manual, SCSI
WORM drive WORM External, Manual, SCSI
IBM 3570 drive 3570 External, Manual, SCSI Atape
IBM 3480, 3490, 3490E drive CARTRIDGE External, Manual, SCSI, ACSLS, 349X
IBM 3590, 3590E drive 3590 External, Manual, SCSI, ACSLS, 349X
IBM LTO 3580 drive LTO External, Manual, SCSI

Table 10. Device Drivers for Automated Libraries

Device Library Type Device Driver
IBM MP 3570, 3575 Library SCSI Atape
IBM LTO 3581, 3583, 3584 Library SCSI
IBM 3494, 3495 Library 349X atldd
Non-IBM SCSI libraries SCSI Tivoli Storage Manager device driver (tsmscsi)

All other supported libraries and drives use the Tivoli Storage Manager device driver. See http://www.tivoli.com/support/storage_mgr/tivolimain.html for a list of supported libraries.

Determining Device Special File Names

To work with removable media devices, Tivoli Storage Manager needs the device's special file name. You specify the device special file name when you issue the DEFINE PATH commands for drives and libraries. You can use SMIT to get the device special file.

When a device configures successfully, a logical file name is returned. Table 11 specifies the name of the device (or the special file name) that corresponds to the drive or library. In the examples, x denotes any number from 0 to 9.

Table 11. Device Examples

Device Device Example Logical File Name
Tape drives that are supported by the Tivoli Storage Manager device driver /dev/mtx mtx
SCSI-attached libraries that are supported by the Tivoli Storage Manager device driver /dev/lbx lbx
Optical drives that are supported by the Tivoli Storage Manager device driver /dev/ropx opx
Drives associated with the GENERICTAPE device type /dev/rmtx rmtx
IBM 3570 devices and the Automatic Cartridge Facility feature of the IBM 3590 B11 as a library /dev/rmtx.smc rmtx
IBM 3575, 3581, 3583, 3584 libraries /dev/smcx smcx
IBM 349X libraries /dev/lmcpx lmcpx
Mount point to use on REMOVABLEFILE device type (CD-ROM) /dev/cdx cdx
Filesystem to use on REMOVABLEFILE device type (zip drive) /zip Not applicable

Attaching the Devices

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

Attaching a Manual Drive

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 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. Attach a terminator to the last device in the chain of devices connected on one SCSI adapter card.
  5. Install the appropriate device driver. See Attaching Devices and Installing Device Drivers.
  6. Find the device worksheet that applies to your device. See http://www.tivoli.com/support/storage_mgr/tivolimain.html.
  7. Determine the name for the device and record the name on the device worksheet. The device name for a tape drive is a special file name. See Determining Device Special File Names.

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

Attaching an Automated Library Device

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.
  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. See http://www.tivoli.com/support/storage_mgr/tivolimain.html.

    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.
  7. Determine the name for the device, which is needed to define the device, 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.

Setting the Library Mode

For Tivoli Storage Manager to access a SCSI library, the device must be set for the appropriate mode. The mode that the server 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 the appropriate mode.

Installing Device Drivers

This section describes how to install the available device drivers.

Installing Device Drivers for IBM SCSI Tape Drives

For IBM 3490, 3570, 358X, and 3590 devices, see IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide for instructions for installing 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 IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers or IBM AIX Parallel and ESCON(R) 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 Device Drivers for Non-IBM Libraries

Use the procedure in this section to configure Tivoli Storage Manager device drivers for autochangers for non-IBM libraries.

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

For SCSI-attached devices:
  1. Select Devices.
  2. Select Tivoli Storage Manager Devices.
  3. Select SCSI Attached Devices.
  4. Select Library/MediumChanger.
  5. Select Add a Library/MediumChanger.
  6. Select the TSM-SCSI-LB for any TSM supported library.
  7. 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.
  8. 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. The SCSI ID and LUN must be separated by a comma (,). For example, a connection address of 4,0 has a SCSI ID=4 and a LUN=0.
  9. 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.

For fibre channel SAN-attached devices:
  1. Select Devices.
  2. Select Tivoli Storage Manager Devices.
  3. Select Fibre Channel SAN Attached Devices.

    This scans the fibre adaptor and configures the devices attached to it.

  4. When the process completes, return to the previous screen and select List Attributes of a Discovered Device.

    The device special file name of each fibre-attached drive is displayed.

Configuring Device Drivers for Non-IBM Tape or Optical Drives

Use the procedure in this section to configure Tivoli Storage Manager device drivers for non-IBM tape or optical drives. See Installing Device Drivers for IBM SCSI Tape Drives.

Attention: Tivoli Storage Manager cannot write over tar or dd tapes, but tar or dd can write over TSM tapes.

Note:
Tape drives can be shared only when the drive is not defined or the server is not started. The MKSYSB command will not work if both Tivoli Storage Manager 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 Tivoli Storage Manager. See your AIX documentation regarding these native device drivers.

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 supported tape drive or TSM-SCSI-OP for any 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. The SCSI ID and LUN must be separated by a comma (,). For example, a connection address of 4,0 has a SCSI ID=4 and a LUN=0.
  8. Click on the DO button. You will receive a message:

Adding a Manual Tape Library to the Server

In the following example, two stand-alone 8mm drives are added to Tivoli Storage Manager. Tivoli Storage Manager requires that all drives are associated with a library. For standalone drives, you must define a manual library. Unlike other library types, no path is defined for manual libraries. 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 PATH
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                                                  |
    |define path server1 drive01 srctype=server desttype=drive                       |
    |library=manuallib device=/dev/mt1 online=yes                                    |
    |define drive manuallib drive02                                                  |
    |define path server1 drive02 srctype=server desttype=drive                       |
    |library=manuallib device=/dev/mt2 online=yes                                    |
    |                                                                                |
    +--------------------------------------------------------------------------------+

    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.
    9. Under Server Storage, select Tape Paths.
    10. From Operations, select Define Drive Path.
    11. Enter the path 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=8mm format=8500 library=manuallib             |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    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.
    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 to the Server

The following example shows how to add an Exabyte EXB-210 library containing two drives. 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 PATH
DEFINE DRIVE
DEFINE PATH
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                                             |
    |define path server1 autolib srctype=server desttype=library                     |
    |device=/dev/lb3 online=yes                                                      |
    |define drive autolib drive05 element=82                                         |
    |define path server1 drive05 srctype=server desttype=drive                       |
    |library=autolib device=/dev/mt5 online=yes                                      |
    |define drive autolib drive06 element=83                                         |
    |define path server1 drive06 srctype=server desttype=drive                       |
    |library=autolib device=/dev/mt6t online=yes                                     |
    +--------------------------------------------------------------------------------+

    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 Server Storage, select Tape Paths.
    7. From Operations, select Define Library Path.
    8. Enter the path information and Finish.
    9. Under Libraries and Drives, select Automated Drives.
    10. From Operations, select Define Automated Drive.
    11. Enter the drive information and Finish.
    12. Under Server Storage, select Tape Paths.
    13. From Operations, select Define Drive Path.
    14. Enter the path 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. Tivoli Storage Manager 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=8mm format=8500 library=autolib               |
    +--------------------------------------------------------------------------------+

    OR
    Web Icon

    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.
    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 they can be used. If you want a volume to be used only when it is requested by name, you must also define it to Tivoli Storage Manager. A defined volume is a private volume and is assigned to a specific storage pool. A volume that is not defined 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 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 Tivoli Storage Manager, 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 the server 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 ]