Administrator's Guide


Configuring Policy for Tivoli Data Protection Application Clients

The Tivoli Data Protection application clients using the server to store data may require that you configure policy to make the most efficient use of server storage. Many of the application clients include a time stamp in each database backup. Because the default policy for the server keeps one backup version of each unique file, database backups managed by default policy are never deleted because each backup is uniquely named with its time stamp. You should configure a new policy for the following application clients:

Tivoli Data Protection for Oracle

Tivoli Data Protection for Microsoft SQL Server

Tivoli Data Protection for Microsoft Exchange

If your server supports both backup-archive clients and any of these application clients, it is recommended that you define a separate policy domain in which the active policy set has a default management class with the required settings for application clients. Then register all application clients to that domain. Do the following:

  1. Create the policy domain for application clients. For example, to define a policy domain that is named APPCLIENTS, enter the following command:
    define domain appclients description='Policy domain for application clients'
    

  2. Create a policy set in that domain. For example, to define the policy set that is named BASE in the APPCLIENTS policy domain, enter the following command:
    define policyset appclients 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 APPCLIENTMC, enter the following command:

    define mgmtclass appclients base appclientmc
    

    Then assign the new management class as the default:

    assign defmgmtclass appclients base appclientmc
    

  4. Define the backup copy group in the default management class, as follows: For example, to define the backup copy group for the APPCLIENTMC management class, enter the following command:
    define copygroup appclients base appclientmc standard destination=diskpool verdeleted=0
    

    In this management class you need only a backup copy group. The application client stores all objects as backup objects on the server. An archive copy group is not required, although it can exist.

  5. Activate the policy set.

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

    activate policyset appclients base
    

  6. Register or update the application clients to associate them with the new policy domain.

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

    update node exch1 domain=appclients
    

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 application client options file to bind all objects to that management class. For example:

include * appclientmc

In this example, appclientmc is the name of the management class that you defined for application clients.

Example of how the policy works: All objects backed up by the application client for Microsoft Exchange are given a unique name; therefore they never expire under default policy. The application client provides a delete function to remove unwanted backup objects from the server. However, for the function to work, the VERDELETED parameter of the backup copy group must be set to 0 (zero). Then, when the application client marks a backup object inactive, that object is deleted from the TSM server the next time expiration processing occurs. A backup object is marked inactive when you delete it through the application client interface.


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