Tivoli Header

Administrator's Guide


Configuring Tivoli Storage Manager for Server-Free Data Movement

The following is an overview for setting up Tivoli Storage Manager for server-free data movement operations:

  1. Step 1. Connect Devices to the Server
  2. Step 2. Determine World Wide Name, Serial Number and LUN
  3. Step 3. Obtaining and Correlating the Disk Information
  4. Step 4. Configuring Tivoli Storage Manager for Server-Free Data Movement:
    1. Enable the server to use server-free data movement using the SET SERVERFREE STATUS=ON command.
    2. Define the library and the path from the server to the library.
    3. Define the tape drives and the paths from the server to the tape drives.
    4. Define the device class.
    5. Define the storage pool.
    6. Create a server-free policy domain.
    7. Define a policy set.
    8. Define the management class and assign it as the default management class.
    9. Define the backup copygroup.
    10. Activate the policy set.
    11. Register the client node.
    12. Define the client disks to the server.
    13. Define the data mover.
    14. Define the paths from the data mover to the tape drives.
    15. Define the paths from the data mover to the client disks.

Step 1. Connect Devices to the Server

Before you begin configuring Tivoli Storage Manager for server-free data movement, you must connect all devices to the SAN or the data mover devices, including:

The devices must exist on the SAN or be attached to the data mover devices prior to defining them to Tivoli Storage Manager. Consult the device documentation for connection instructions, or visit http://www.tivoli.com/support/storage_mgr/tivolimain.html.

Step 2. Determine World Wide Name, Serial Number and LUN

Before you can configure Tivoli Storage Manager for server-free data movement, you must first identify and record the world wide name, serial number, and LUN of each disk device and tape drive used, and the world wide name and serial number of the data mover. This information will be used when defining devices and device paths. To do this, issue the QUERY SAN command. The QUERY SAN command will display the devices that can be detected on the SAN, as well as the information for those devices. For example, if you wanted to find the world wide name, the serial number, and the LUN for each device on your SAN, you would issue the following:

query san format=detailed

The output would list every device detected on the SAN, and the corresponding information detected for that device. The following illustrates the output for a disk and a tape drive detected on the SAN:

+--------------------------------------------------------------------------------+
|                                                                                |
|                        Device Type: DISK                                       |
|                             Vendor: IBM                                        |
|                            Product: DDYF-T18350R                               |
|                             Serial: TEF76061                                   |
|                             Device:                                            |
|                          DataMover: No                                         |
|                           Node WWN: 5005076206039E05                           |
|                           Port WWN: 5005076206439E05                           |
|                                Lun: 0                                          |
|                          SCSI Port: 3                                          |
|                           SCSI Bus: 0                                          |
|                        SCSI Target: 0                                          |
|                                                                                |
|                        Device Type: DRIVE                                      |
|                             Vendor: IBM                                        |
|                            Product: 03570B02                                   |
|                             Serial: 67IU984T3                                  |
|                             Device: mt10.2.0.3                                 |
|                          DataMover: No                                         |
|                           Node WWN: 2002006045160D2A                           |
|                           Port WWN: 2002006045160D2A                           |
|                                Lun: 2                                          |
|                          SCSI Port: 3                                          |
|                           SCSI Bus: 0                                          |
|                        SCSI Target: 10                                         |
|                                                                                |
+--------------------------------------------------------------------------------+

When you record the information, be sure to use Port WWN as the world wide name, and Lun as the LUN to be used in the path definitions. For example, the information you would record for your tape drive would be:

There may be additional methods of discovering the world wide name, serial number and LUN, depending on what type of Fibre Channel host bus adapter and data mover device you are using. Consult the manufacturer of the product for more information.

For more information about QUERY SAN, see Tivoli Storage Manager for Windows Administrator's Reference.

Step 3. Obtaining and Correlating the Disk Information

Once you have detected and recorded the information for all of the devices detectable on the SAN, you must obtain and correlate the information for the disks that you will be backing up to the owning client nodes. This is necessary to ensure that only one client node will be able to perform a server-free backup or restore operation for any given disk in the SAN.

  1. Log into the client machine that owns the disk and start the Tivoli Storage Manager backup/archive client.
  2. Issue the QUERY DISKINFO command on the Tivoli Storage Manager client. There are two ways that the QUERY DISKINFO command will display the information for disks associated with the client. You can either query to have the information displayed for every disk associated with the client, or query to display the disks that a specific volume is located on. In this example we will display the information for all disks associated with the client named BELFAST:
    query diskinfo
    

    The output will contain the information needed for correlating the disk information:

    +--------------------------------------------------------------------------------+
    | Disk name        LUN            Serial number                                  |
    |-------------     -----------    -------------                                  |
    |Harddisk0         0              TEF76061                                       |
    |Harddisk1         1              GH089673                                       |
    |Harddisk2         2              TEF78893                                       |
    |                                                                                |
    +--------------------------------------------------------------------------------+
    Note:
    The output of the QUERY DISKINFO client-command will display the information of every disk defined to the client, regardless of whether they exist on the SAN.
  3. Compare the information from the QUERY DISKINFO client-command output to the output of the QUERY SAN command. In this example, the serial number and LUN from the disk, Harddisk0, match the information for the disk displayed in the output from the QUERY SAN command, indicating that this is the disk to be backed up. When you record the needed information, be sure to use Port WWN as the world wide name, and Lun as the LUN to be used in the path definitions. The information you would record for the disk that will be backed up with server-free is:

For more information about the client command, QUERY DISKINFO, see Backup-Archive Installation and User's Guide.

Step 4. Configuring Tivoli Storage Manager for Server-Free Data Movement

  1. Enable the server to perform server-free data movement operations using the SET SERVERFREE command:
    set serverfree status=on batchsize=500
    
    For more information on BATCHSIZE, see Managing Server-Free Data Movement.
  2. Define the library to the server by using the DEFINE LIBRARY command. In this example, define an unshared library named SCSILIB:
    define library scsilib libtype=scsi shared=no
    
  3. Define the library path from the server to the library by using the DEFINE PATH command:
    define path server1 scsilib srctype=server desttype=library
     device=lb10.3.0.3
    

    The DEVICE parameter specifies the device driver's name for the library, which is the special file name.

    The device special file name may be displayed in the output of the QUERY SAN command, see Step 2. Determine World Wide Name, Serial Number and LUN. For more information about device special file names, see Using Device Alias Names. For more information about paths, see Defining Paths.

  4. Define the drives to the server by using the DEFINE DRIVE command. In this example, define the drive named DRIVE1, which has a world wide name of 2002006045160D2A and a serial number of 67IU984T3:
    define drive scsilib drive1 element=16 wwn=2002006045160d2a
     serial=67iu984t3
    

    To determine the world wide name and serial number of the drive, see Step 2. Determine World Wide Name, Serial Number and LUN. For more information about defing drives, see Defining Drives.

  5. Define the drive paths from the server to the drive by using the DEFINE PATH command:
    define path server1 drive1 srct=server desttype=drive library=scsilib 
     device=mt10.2.0.3
    

    The DEVICE parameter specifies the name for the drive, which is the special file name, used by the device driver.

    The device special file name may be displayed in the output of the QUERY SAN command, see Step 2. Determine World Wide Name, Serial Number and LUN. For more information about device special file names, see Using Device Alias Names. For more information about paths, see Defining Paths.

  6. Define the device class to the server by using the DEFINE DEVCLASS command. The device class in this example is SCISICLASS:
    define devclass scsiclass devtype=3570 library=scsilib
    

    See Defining and Updating Device Classes for Tape Devices.

  7. Define the storage pools to the server by using the DEFINE STGPOOL command. In this example, add the storage pool named SRVFREEPOOL:
    define stgpool srvfreepool scsiclass maxscratch=5
     dataformat=nonblock
    
    Note:
    The data format must be defined as NONBLOCK for server-free data movement.

    For more information, see Data Format for Server-Free Data Movement.

  8. Create a policy domain for server-free data movement. For example, to define a policy domain that is named SFDOMAIN, enter the following command:
    define domain sfdomain
     description='Policy domain for server-free data movement'
    
  9. Define a policy set in that domain. For example, to define a policy set named STANDARD in the policy domain named SFDOMAIN, enter the following:
    define policyset sfdomain standard
    
  10. Define the management class by using the DEFINE MGMTCLASS command. In this example, define a management class named SF1 in the STANDARD policy set:
    define mgmtclass sfdomain standard sf1
    

    For more information about management classes, see Chapter 14, Implementing Policies for Client Data.

  11. Assign the management class as the default management class for the policy set. In this example, assign the management class SF1 as the default:
    assign defmgmtclass sfdomain standard sf1
    
  12. Define a backup copy group with the server-free storage pool, SRVFREEPOOL, as the destination by issuing the DEFINE COPYGROUP command:
    define copygroup sfdomain standard sf1 type=backup
     destination=srvfreepool
    

    For more information about copy groups, see Chapter 14, Implementing Policies for Client Data.

  13. Activate the policy set in the SFDOMAIN policy domain by issuing the ACTIVATE POLICYSET command:
    activate policyset sfdomain standard
    

    For more information on policy sets, see Chapter 14, Implementing Policies for Client Data.

  14. Register the client node BELFAST as a Tivoli Storage Manager node, as well as the password CLIENTPASS, to the domain SFDOMAIN by issuing the REGISTER NODE command:
    register node belfast clientpass domain=sfdomain
    

    For more information on client nodes, see Chapter 12, Adding Client Nodes.

  15. Define each disk using the DEFINE DISK command. Use the information obtained in Step 2. Determine World Wide Name, Serial Number and LUN and Step 3. Obtaining and Correlating the Disk Information:
    define disk belfast Harddisk0 wwn=5005076206439e05 serial=tef76061
    
  16. Define the data mover by using the DEFINE DATAMOVER command. In this example, define the datamover SCSI1:
    define datamover scsi1 type=scsi wwn=2002006045160d2a serial=21081300957 
     dataformat=nonblock copythreads=5  
    
    To determine the world wide name and serial number of the data mover, see Step 2. Determine World Wide Name, Serial Number and LUN. For more information on COPYTHREADS, see Managing Server-Free Data Movement.
  17. Define the paths from the data mover to the drive using the DEFINE PATH command.
    define path scsi1 drive1 srctype=datamover desttype=drive 
     library=scsilib lun=2
    

    These paths are defined in order to allow the drives to be used for server-free data movement operations. For more information about paths, see Defining Paths. To determine the LUN for the path, see Step 2. Determine World Wide Name, Serial Number and LUN.

  18. Define the paths from the data mover to each disk using the DEFINE PATH command.
    define path scsi1 Harddisk0 srctype=datamover desttype=disk 
     node=belfast lun=0
    

    These paths are defined in order to allow the disks to be used for server-free data movement operations. For more information about paths, see Defining Paths. To determine the LUN for the path, see Step 2. Determine World Wide Name, Serial Number and LUN.

  19. You must label the tapes and check the tapes into the tape library. These tasks are the same as for other libraries. See Labeling Media for more information.


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