Tivoli Storage Manager for Sun Solaris Administrator's Guide


Configuring Policy for Managed System for SAN

With the Managed System for SAN feature, you can set up a SAN configuration in which a TSM client directly accesses a library device to read or write data. SAN data transfer requires setup on the server and on the client, and the installation of a storage agent on the client machine. The storage agent transfers data between the client and the storage device. See TSM Managed System for SAN Storage Agent User's Guide for details. See the Web site for details on clients that support the feature: http://www.tivoli.com/support/storage_mgr/tivolimain.html .

One task in configuring your systems to use this feature is to set up policy for the clients. Copy groups for these clients must point to the storage pool that is associated with the SAN devices. (Configuring TSM Clients to Directly Access SAN-Attached Devices describes how to configure the devices and define the storage pool.) Clients for which you have mapped the SAN drives in this storage pool can then use the SAN to send data directly to the device for backup, archive, restore, and retrieve.

One way to configure policy for clients is to define a separate policy domain in which the active policy set has a default management class with the required settings. Then register all clients using SAN data transfer to that domain. Do the following:

  1. Create the policy domain for the clients. For example, to define a policy domain that is named SANCLIENTS, enter the following command:
    define domain sanclients
     description='Policy domain for clients using SAN devices'
    
  2. Create a policy set in that domain. For example, to define the policy set that is named BASE in the SANCLIENTS policy domain, enter the following command:
    define policyset sanclients base
    
  3. Create the default management class for the policy set. First define the management class, then assign the management class as the default for the policy set.

    For example, to define the management class that is named SANCLIENTMC, enter the following command:

    define mgmtclass sanclients base sanclientmc
    

    Then assign the new management class as the default:

    assign defmgmtclass sanclients base sanclientmc
    
  4. Define the backup copy group in the default management class, as follows: For example, to define the backup copy group for the SANCLIENTMC management class, enter the following command:
    define copygroup sanclients base sanclientmc standard destination=sanpool
    
  5. Define the archive copy group in the default management class, as follows: For example, to define the archive copy group for the SANCLIENTMC management class, enter the following command:
    define copygroup sanclients base sanclientmc standard
     type=archive destination=sanpool
    
  6. Activate the policy set.

    For example, to activate the BASE policy set in the SANCLIENTS policy domain, enter the following command:

    activate policyset sanclients base
    
  7. Register or update the application clients to associate them with the new policy domain.

    For example, to update the node SANCLIENT1, enter the following command:

    update node sanclient1 domain=sanclients
    

If you choose not to define a separate policy domain with the appropriate management class as the default, you must define a new management class within an existing policy domain. Because the new management class is not the default for the policy domain, you must add an include statement to each client options file to bind all objects to that management class. For example, suppose sanclientmc is the name of the management class that you defined for clients that are using devices on a SAN. You want the client to be able to use the SAN for backing up any file on the c drive. Put the following line at the end of the client's include-exclude list:

include c:* sanclientmc

For details on the include-exclude list, see Tivoli Storage Manager Installing the Clients.


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