Administrator's Guide


Installing Device Drivers

For TSM to use a device, you must install the appropriate device driver.

IBM tape drives, tape autochangers, and tape libraries
Install the IBMtape device driver. 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
You must ensure that you have installed the TSM device drivers. When you install TSM, you must choose whether to install the TSM device drivers for tape and tape autochanger devices.

Optical devices
Install the TSM device drivers. See http://www.tivoli.com/tsm .

Other removable media devices
See Configuring Removable Media Devices.

Before You Start: Names for Devices

To identify and work with removable media devices, TSM needs the device's special file name. For devices other than the IBM 3494, the name is the special file name. For a 3494, the device name is the symbolic name you entered in the configuration file for the library.

During configuration of devices other than the 3494, one or more device special file names are created. The following table shows the form of the names. In this table, x denotes a number (0-7).

Special File Name Description
/dev/rmt/xmt Used for tape drives that are supported by the TSM device driver
/dev/rmt/xlb Used for SCSI-attached libraries that are supported by the TSM device driver
/dev/rmt/xop Used for optical drives that are supported by the TSM device driver
/dev/rmt/xst Used for IBM 3490, 3570, and 3590 tape drives, which are supported by the IBMtape device driver
/dev/rmt/xsmc Used for the medium changer (the robotics) of an IBM 3570 or an IBM 3590 B11 with Automatic Cartridge Facility (ACF) feature, which are supported by the IBMtape device driver

The special file is a symbolic link into the /devices tree of the file system. The symbolic link destination has the form:

/devices/.../mt@x,0:mt

where x is the SCSI ID of the device.

The following are examples of special file names:

Table 5. Examples of Device Special File Names

If the logical file name is: The device special file name is:
3mt /dev/rmt/3mt
0lb /dev/rmt/0lb
1op /dev/rmt/1op
2st Drive: /dev/rmt/2st

Medium changer: /dev/rmt/2smc (3570 or 3590 B11 with ACF)

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, a set of special file names are available for each device. To see the special file names, use the command

ls -la /dev/rmt

The output shows that the special files are really symbolic links into the /devices tree of the file system.

Installing Device Drivers for IBM 349X Libraries

For an IBM 3494 Tape Library Dataserver, use the information in IBM SCSI Device Drivers: Installation and User's Guide to install the driver. The driver is the IBM Tape Library Driver for Sun Solaris, which consists of the lmcpd (a daemon) and other components.

To determine the name to use to define the library to TSM, check what you entered in the /etc/ibmatl.conf file for the library's symbolic name. Use this information to complete the Device Name field on your worksheet.

For example, if the symbolic name for the library in the /etc/ibmatl.conf file is 3494a, enter that name on the worksheet in the Device Name field for the library.

The drives that are in the library are set up separately. See Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives.

Installing Device Drivers for Non-IBM Tape Drives and Libraries

To use the TSM device drivers, you must first edit configuration files that reside in the /usr/kernel/drv directory, and then issue the ADD_DRV (add drive) command. The devices should already be connected to the system and powered on.

If you are configuring a tape library, you must set up the device drivers for both the drives in the library and the library itself (that is, the robotics).

Installing the Tivoli Storage Manager Device Driver for Tape Drives

To install the TSM device driver for tape drives, perform the following steps:

  1. Verify that the device is connected to your system, and is powered on and active.

  2. Edit the /usr/kernel/drv/mt.conf file. Add one stanza (as shown in the example at the top of the file) for each TSM tape drive in the system that you want the TSM server to use.

  3. Log in as root user.

  4. Add the drive by entering the following command:
    > /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt
    

  5. Determine the special file names for the tape drives.

    The device special files for the tape drives appear in the /dev/rmt directory. Their names have the form /dev/rmt/xmt, where x is a number. To determine the relationship between a physical device and the special file that was created for it, issue the following command:

    > ls -l /dev/rmt/*mt
    

    The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../mt@x,0:mt, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xmt special file names to provide to the server when you issue a DEFINE DRIVE command.

  6. Record the SCSI IDs and special file names on the worksheets. See http://www.tivoli.com/tsm .

Installing the Tivoli Storage Manager Device Driver for Tape Libraries

To install the TSM device driver for tape libraries, perform the following steps:

  1. Edit the /usr/kernel/drv/lb.conf file. Add one stanza (as shown in the example at the top of the file) for each TSM autochanger device in the system that you want the TSM server to use.

  2. Log in as root user.

  3. Add the library by entering the following command:
    > /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
    

  4. Determine the special file names for the tape libraries.

    The device special files for libraries appear in the /dev/rmt directory. Their names have the form /dev/rmt/xlb, where x is a number. To determine the relationship between a physical device and the special file that was created for it, issue the following command:

    > ls -l /dev/rmt/*lb
    

    The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE LIBRARY command.

  5. Record the SCSI IDs and special file names on the worksheets. See http://www.tivoli.com/tsm .

Installing Device Drivers for Optical Devices

To use the TSM device drivers, you must first edit configuration files that reside in the /usr/kernel/drv directory, and then issue the ADD DRIVE command. The devices should already be connected to the system and powered on.

If you are configuring a tape library, you must set up the device drivers for both the drives in the library and the library itself (that is, the robotics) for TSM to use.

Installing the Tivoli Storage Manager Device Driver for Optical Drives

To install the TSM device driver for optical drives, perform the following steps:

  1. Verify that the device is connected to your system, and is powered on and active.

  2. Edit the /usr/kernel/drv/op.conf file. Add one stanza (as shown in the example at the top of the file) for each TSM tape drive in the system that you want the TSM server to use.

  3. Log in as root user.

  4. Add the drive by entering the following command:
    /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/op
    

  5. Determine the special file names for the drives.

    The device special files for the optical drives appear in the /dev/rmt directory. Their names have the form /dev/rmt/xop, where x is a number. To determine the relationship between a physical device and the special file that was created for it, issue the following command:

    ls -l /dev/rmt/*op
    

    The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../op@x,0:op, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xop special file names to provide to the server when you issue a DEFINE DRIVE command.

  6. Record the SCSI IDs and special file names on the worksheets. See http://www.tivoli.com/tsm .

Installing the Tivoli Storage Manager Device Driver for Optical Libraries

To install the TSM device driver for a library, perform the following steps:

  1. Edit the /usr/kernel/drv/lb.conf file. Add one stanza (as shown in the example at the top of the file) for each TSM autochanger device in the system that you want the TSM server to use.

  2. Log in as root user.

  3. Add the library by entering the following command:
    > /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
    

  4. Determine the special file names for the tape libraries.

    The device special files for libraries appear in the /dev/rmt directory. Their names have the form /dev/rmt/xlb, where x is a number. To determine the relationship between a physical device and the special file that was created for it, issue the following command:

    > ls -l /dev/rmt/*lb
    

    The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE LIBRARY command.

  5. Record the SCSI IDs and special file names on the worksheets. See http://www.tivoli.com/tsm .

Configuring Removable Media Devices

Support for removable file devices allows portability of media between UNIX systems. It also allows this media to be used to transfer data between systems that support the media. Removable file support allows TSM to read data from a FILE device class that is copied to removable file media through third-party software. The media is then usable as input media on a target TSM server that uses the REMOVABLEFILE device class for input.

Note:Software for writing CD-ROMs may not work consistently across platforms.

Use a MAXCAPACITY value that is less than one CD-ROM's usable space to allow for a one-to-one match between files from the FILE device class and copies that are on CD-ROM. Use the DEFINE DEVCLASS or UPDATE DEVCLASS commands to set the MAXCAPACITY parameter of the FILE device class to a value less than 650MB.

Example of Removable File Support

Use these steps as an example of TSM REMOVABLEFILE (CD-ROM) support. This example takes an export object and moves it from one server to another.

Server A

  1. Define a device class with a device type of FILE.
    define devclass file devtype=file directory=/home/user1
    

  2. Export the node. This command results in a file name /home/user1/CDR03 that contains the export data for node USER1.
    export node user1 filedata=all devclass=file vol=cdr03
    

    You can use software for writing CD-ROMs to create a CD with volume label CDR03 that contains a single file that is also named CDR03.

Server B

  1. Follow the manufacturer's instructions to attach the device to your server.

  2. Sun Solaris automatically mounts the CD as a removable file system, but the mount options are not correct. Unmount the CD-ROM with the following command:
    umount /cdrom/cdrom0
    

  3. Issue this command on your system to mount the CD-ROM.
    mount -F hsfs -o ro,nomaplcase,notraildot /vol/dev/dsk/c0t6d0/cdr03 /cdrom/cdr03
    

    -F hsfs
    Specifies that the media has a CD file system

    -o
    Specifies the options on the mount

      ro
    Specifies a read-only file system

      nomaplcase
    Specifies that file names do not map to lower case

      notraildot
    Specifies that file names do not require a trailing dot when no extension is present

    /vol/dev//dsk/c0t6d0/cdr03
    Specifies the physical description of the CD-ROM on the system

      c0
    Specifies SCSI controller 0

      t6
    Specifies SCSI ID 6

      d0
    Specifies SCSI LUN ID 0

      cdr03
    Specifies the volume label of the CD

    /cdrom/cdr03
    Specifies the mount point of the first CD-ROM drive
    Note:CD-ROM drives lock while the file system is mounted. This prevents use of the eject button on the drive. You must issue the EJECT CDROM command to remove a CD-ROM from the drive.

  4. Ensure that the media is labeled. The software that you use for making a CD also labels the CD. Before you define the drive, you must put formatted, labeled media in the drive. For label requirements, see Labeling Requirements for Optical and Other Removable Files Devices. When you define the drive, TSM verifies that a valid file system is present.

  5. Define a library that is named CDROM. The library type must be MANUAL.
    define library cdrom libtype=manual
    

  6. Define a drive named CDDRIVE at mount point /cdrom/cdrom0.
    define drive cdrom cddrive device=/cdrom/cdrom0
    

  7. Define a device class with a device type of REMOVABLEFILE. The device type must be REMOVABLEFILE.
    define devclass cdrom devtype=removablefile library=cdrom
    

  8. Issue the following TSM command to import the node data on the CD-ROM volume CDR03.
    import node user1 filedata=all devclass=cdrom vol=cdr03
    

Labeling Requirements for Optical and Other Removable Files Devices

TSM does not provide utilities to format or label media for the REMOVABLEFILE device type. You must use another application to copy the FILE device class data to the CD-ROM to a file that has the same name as the volume label. This software also labels the removable media.

The label on the media must meet the following restrictions:


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