Transitioning SQL Server backups from Tivoli Storage FlashCopy® Manager to Tivoli Storage Manager

News


Abstract

Tivoli Storage FlashCopy® Manager works when connected to the local Tivoli Storage FlashCopy® Manager server or a Tivoli Storage Manager server. The Tivoli Storage Manager server can be located anywhere on your network. The FlashCopy® Manager Snapin includes two configuration wizards. These enable you to do a local configuration and a Tivoli Storage Manager configuration. You can move from one type of server to another by running the corresponding configuration wizard at any time. This document describes a way to configure Tivoli Storage FlashCopy® Manager so that you can access both a local and Tivoli Storage Manager server at the same time. This might be useful if you decide to move to a Tivoli Storage Manager environment and want to continue to interact with the locally managed snapshots until policy marks them for expiration.

Content

Do these tasks on the Tivoli Storage Manager server

Coordinate efforts with your Tivoli Storage Manager server administrator to get these tasks completed:

  1. Select or create the policy definitions that will be used for each type of backup you plan to use. You can provide the administrator with the existing locally-defined policy settings in your Tivoli Storage FlashCopy® Manager stand-alone environment. Use the GUI or the command-line interface of Data Protection for Microsoft SQL Server to retrieve this information.

  2. Register your Data Protection for SQL node name and password with the Tivoli Storage Manager register node command. For example:

    register node <DPnodename> <DPpassword>

  3. If not already defined in the Tivoli Storage Manager server, register the Tivoli Storage Manager backup-archive client node name and password for the workstation where the SQL server is installed. For example:

    register node <BAnodename> <BApassword>

  4. Define the proxy node relationship for the Target Node and agent nodes with the Tivoli Storage Manager grant proxynode command. For example:
    grant proxynode target=DP agent=BAnodename


Implement these tasks on the workstation running the SQL Server

  1. In the directory where the Data Protection for Microsoft SQL Server is installed, make a copy of the options file named dsm.opt. After you begin using the Tivoli Storage Manager server, the copy is used for access to the FlashCopy® Manager stand-alone environment. One method of making the copy is to start the SQL command line prompt from the FlashCopy® Manager Snapin:

    In the FlashCopy® Manager Snapin Tree view, a SQL server node is displayed for each SQL server instance on the computer.
    1. Select an SQL server instance in the tree view. The integrated command line and an Actions pane is displayed.
    2. Launch the Data Protection for SQL command line from the Actions pane. Select:

      Launch Command Line

    3. To make a copy of the options file, enter:

      copy dsm.opt dsm_local.opt

  2. In the same directory, make a copy of the Data Protection for SQL configuration file. For example:

    copy tdpsql.cfg tdpsql_local.cfg

    Preserve the contents of the local configuration file if:
    1. you have specified policy bindings during the use of FlashCopy® Manager.
    2. you will be updating the policy bindings to reflect changes in your policy specifications for your TSM Server usage.
  3. In the Tivoli Storage Manager backup-archive client installation directory, make a copy of the VSS requestor options file named dsm.opt. Use the Windows copy command. For example:

    C:\Program Files\Tivoli\TSM\baclient>copy dsm.opt dsm_local.opt

  4. In all of the files named dsm.opt, modify the TCPSERVERADDRESS line. Replace FLASHCOPYMANAGER with the IP address of the Tivoli Storage Manager server. For example:

    TCPServeraddress 9.52.170.67

    To accomplish this task, use a text editor like Notepad or Wordpad.

  5. To access the FlashCopy® Manager stand-alone environment during the transition period, open a Windows command prompt and change the directory to the Tivoli Storage Manager backup-archive client installation directory. The default is:
    C:\Program Files\Tivoli\TSM\baclient


    Create an alternate Windows service for the Tivoli Storage Manager Client Acceptor service by using the dsmcutil command. For example:

    dsmcutil install cad /name:tsmcad4local
    /node:my_backup-archive_client_node
    /password:my_TSM_server_password
    /optfile:”C:\Program Files\Tivoli\TSM\baclient\dsm_local.opt”
    /httpport:1583

    For more information on using the dsmcutil command, refer to the information on using the client service configuration utility in the Tivoli Storage Manager Windows Backup-Archive Clients Installation and User’s Guide.

  6. Create an alternate Windows service for the Tivoli Storage Manager remote agent service. For example:

    dsmcutil install remoteagent /name:tsmagent4local
    /node:my_backup-archive_client_node
    /password:my_TSM_server_password
    /optfile:”C:\Program Files\Tivoli\TSM\baclient\dsm_local.opt”
    /partnername:tsmcad4local

  7. Edit the dsm_local.opt file in the Data Protection for SQL installation directory. Add this line:
    HTTPPORT 1583

  8. Start the alternate Tivoli Storage Manager Client Acceptor service:

    dsmcutil start /name:tsmcad4local

  9. Stop and restart the original Tivoli Storage Manager Client Acceptor service so that the new values in the dsm.opt file are activated. You can do this through the Windows Services GUI or by using the dsmcutil command:

    dsmcutil stop /name:”TSM Remote Client Agent”
    dsmcutil stop /name:”TSM Client Acceptor”
    dsmcutil start /name:”TSM Client Acceptor”

  10. As backups start occurring and are managed in the Tivoli Storage Manger server environment, you will need to phase out the remaining backups created in the FlashCopy® Manager stand-alone environment. You can choose between two ways of achieving the phase-out:
    1. In the FlashCopy® Manager stand-alone environment, define a time-based policy that will automatically cause the old backups to expire and be deleted . For example, if you want to expire each backup after it is 30 days old, update the time-based policy by using the command:

      tdpsqlc update policy mypolicy /daysretain=30
      /tsmoptfile=dsm_local.opt
      /configfile=tdpsql_local.cfg

      You can also make this change using the Local Policy Management dialog that is accessed from the Utilities menu of the Data Protection for Exchange Backup/Restore GUI. Information on how to start the GUI is located below in the section describing how to access the FlashCopy® Manager stand-alone environment.

      The process of expiring backups when their age exceeds the daysretain limit depends upon a basic function that is run in the stand-alone environment. The function must include an operation that queries the backups.

      If you will not be regularly using the stand-alone environment client, you can use a scheduler to periodically start a command such as:

      tdpsqlc query tsm * /all
      /tsmoptfile=dsm_local.opt
      /configfile=tdpsql_local.cfg

      For example, if your backups are created each week, then you can schedule the query command above to run once a week in order to cause the expiration of out-of-date backups.

      The very last backup, that is created while running the stand-alone environment, will not be automatically deleted by the process of expiring the backups. For that, you will need to use the explicit delete operation, as described next.

    2. Alternatively, you can explicitly delete each backup when you determine that it is no longer needed. Use the Data Protection for SQL delete backup command, or the Delete Backup (right mouse-click menu option) in the GUI Restore window.

  11. To access the FlashCopy® Manager stand-alone environment:
    1. Start the SQL Client – Command Line prompt.

    2. Start FlashCopy® Manager stand-alone commands by appending the /tsmoptfile option, for example:

      tdpsqlc query tsm * /all
      /tsmoptfile=dsm_local.opt
      /configfile=tdpsql_local.cfg

    3. Start the GUI (from the Command Line prompt) by issuing the GUI invocation command, for example:

      tdpsql /tsmoptfile=dsm_local.opt
      /configfile=tdpsql_local.cfg

  12. If necessary, start the FlashCopy® Manager stand-alone environment to restore from a backup that was created in that environment.

  13. When the transition is complete and you no longer need to access the FlashCopy® Manager stand-alone environment, you can remove the alternate services. To do this, use the Windows Services GUI or the dsmcutil command:

    dsmcutil remove /name:tsmagent4local
    dsmcutil remove /name:tsmcad4local

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager for Databases
Data Protection for MS SQL

Software version:

5.5

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1394724

Modified date:

2010-07-08

Translate my page

Machine Translation

Content navigation