Configuring Tivoli Storage FlashCopy Manager for file system and custom application on a Microsoft Cluster Server environment

The following steps are required to configure a Tivoli® Storage FlashCopy® Manager for file system and custom application support workload for a Microsoft Cluster Server environment. Before initiating the configuration, read the entire procedure.

About this task

The configuration steps must be performed in the same precise manner on all of the nodes in the cluster. The steps also show you how to configure multiple cluster resource groups containing physical disk resources.

Keep the number of cluster groups to a minimum. If possible, have only one cluster resource group contain all physical disk resources. Also, use a dedicated volume (VSS staging directory volume) for each cluster resource group. The VSS staging directory volume must have a minimum of 1 GB of storage space for FlashCopy Manager metadata. This volume must be part of the cluster resource group and must be able to failover with the cluster resource group. This VSS staging directory volume should not be one of the volumes that gets backed up with Tivoli Storage FlashCopy Manager.

Complete the following steps for each node on the cluster:

Procedure

  1. Install Tivoli Storage FlashCopy Manager.
  2. Launch the Tivoli Storage FlashCopy Manager MMC GUI.

    You are automatically prompted to run the configuration wizard. If the configuration wizard prompt is not displayed automatically, expand the following tree nodes:IBM Tivoli Storage Manager > Dashboard > Manage > Configuration. Then, select Wizards. Depending on your environment, launch either the Standalone Configuration or TSM Configuration wizard. If you have a Tivoli Storage Manager server, select TSM Configuration, otherwise, if you do not have access to a Tivoli Storage Manager server, select Standalone Configuration.

  3. Select the File System checkbox. To start the wizard, click Next.
    • For the Standalone Configuration, complete the following steps:
      1. On the requirements check panel, for the Cluster check rule, you might see a Warnings link. Click Warnings and the MMC displays the Issue Resolution Windows for vssaltstagingdir path. In this Path dialog box, enter the path of your VSS staging directory volume as described above. If you are configuring multiple resource groups, start with the dedicated volume belonging to the cluster resource group you want to configure first.
      2. Complete the wizard pages.
      3. Click Finish to complete the initial configuration.
      4. After the configuration wizard completes, the following are the contents of the different options files. Values might differ slightly:
        • In the backup-archive client options file:
          NODename OTHELLO 
          PASSWORDAccess generate 
          TCPServeraddress flashcopymanager 
          HTTPport 1581
          CLUSTERnode no 
          CLUSTERDISKSOnly no 
          VSSALTSTAGINGDIR J:\vssaltstagingdir
        • In the Tivoli Storage FlashCopy Manager file system options file:
          NODename OTHELLO_FS 
          PASSWORDAccess generate 
          TCPServeraddress flashcopymanager 
          HTTPport 1581 
          CLUSTERnode yes 
          VSSALTSTAGINGDIR J:\vssaltstagingdir
      5. Exit the MMC GUI.
    • For the TSM Configuration, complete the following steps:
      1. On the requirements check panel, for the Cluster check rule, you might see a Warnings link. Click Warnings and the MMC displays the Issue Resolution Windows for vssaltstagingdir path. In this Path dialog box, enter the path of your VSS staging directory volume as described above. If you are configuring multiple resource groups, start with the dedicated volume belonging to the cluster resource group you want to configure first.
      2. Complete the required information.
      3. Click Finish to complete the initial configuration.
      4. After the configuration wizard is complete, the following contents are displayed in the different options files. Values might differ slightly. In the following OPT files, make sure the DSM agent node and Tivoli Storage FlashCopy Manager node have already been registered and granted proxy.
        • In the backup-archive client options file:
          NODename OTHELLO 
          PASSWORDAccess generate 
          TCPServeraddress orion.storage.usca.ibm.com 
          TCPPort 1500 
          CLUSTERnode no 
          CLUSTERDISKSOnly no 
        • In the Tivoli Storage FlashCopy Manager file system options file:
          NODename CLUSTER_FS 
          PASSWORDAccess generate 
          TCPServeraddress orion.storage.usca.ibm.com 
          TCPPort 1500 
          HTTPport 1581 
          CLUSTERnode yes 
          VSSALTSTAGINGDIR J:\vssaltstagingdir
      5. Exit the MMC GUI.
      6. Open a Windows command prompt and change the directory to the backup-archive client directory. Default location: c:\Program Files\Tivoli\tsm\baclient
      7. To connect to the Tivoli Storage Manager server, issue the dsmc command . You might need to provide your user ID and password for the backup-archive client DSMAGENT node to save the password on the registry. Exit the dsmc.
      8. Using the same Windows command prompt, enter the following command to connect to the Tivoli Storage Manager server using the Tivoli Storage FlashCopy Manager node:
        dsmc -optfile="c:\Program Files\Tivoli\FlashCopyManager\dsm.opt" 
        You might need to provide your user ID and password for the Tivoli Storage FlashCopy Manager node to save the password on the registry. Exit the dsmc and exit the Windows command prompt.
  4. (Standalone Configuration only) Complete the following steps:
    1. Open the Windows Services MMC. Stop both the CAD and Agent Services named, by default, TSM Client Acceptor and TSM Remote Client Agent, respectively.
    2. Open a Windows command prompt and change directories to the Tivoli Storage FlashCopy Manager installation directory. The default location: C:\Program Files\Tivoli\FlashCopyManager
    3. Open the dsm.opt file using Notepad and change the nodename option to a different name that would best describe your cluster. For example: NODEname cluster_fs
    4. Specify the VSS staging directory volume for Tivoli Storage FlashCopy Manager VSS metadata. Add the vssaltstagingdir path option at the end of the file. The path should be the path of your VSS staging directory volume as described above. If you are configuring multiple resource groups, start with the dedicated volume belonging to the cluster resource group that you want to configure first. For example, if the J: drive is the dedicated VSS staging directory volume belonging to the cluster resource that you want to configure, specify the option like the following example:
      VSSALTSTAGINGDIR J:\vssaltstagingdir
    5. Save and close the Tivoli Storage FlashCopy Manager options file.
    6. Change the directory to the backup-archive client installation directory. Default location: C:\Program Files\Tivoli\tsm\baclient
    7. Open the dsm.opt file using Notepad and add the exact same value for the vssaltstagingdir option as in the Tivoli Storage FlashCopy Manager dsm.opt file. For example:
      VSSALTSTAGINGDIR J:\vssaltstagingdir
    8. Save and close the backup-archive client options file.
    9. Exit the Windows command prompt.
  5. If this node is the first cluster node that you are configuring, open the Microsoft Failover Cluster Manager. Go to the cluster resource group that you are configuring. Right click on the resource group and select Add a resource > Generic Service. From the New Resource Wizard dialog that is displayed, select the CAD service, named, by default, TSM Client Acceptor, and continue the wizard until finished. Bring the TSM Client Acceptor service resource online from the Failover Cluster Manager. If you are repeating this procedure for another cluster node, the TSM Client Acceptor service resource has already been configured. In this scenario, go to the resource group and bring up the service resource online.
  6. Open a Windows command prompt and change directories to the Tivoli Storage FlashCopy Manager installation directory. Default location: C:\Program Files\Tivoli\FlashCopyManager
    Issue the following command:
    fcmcli query component
    A list of all available volumes for backup is displayed.
  7. You have just configured your first group resource. If you only have one resource group, you are finished. Complete the same procedure on the other nodes in your cluster. Before you begin the procedure on other nodes in the cluster, go to the Windows Services MMC, and stop, if running, the TSM Remote Client Agent service created in this procedure. Then, using the Microsoft Failover Cluster Manager, make the TSM Client Acceptor service offline from the resource group just configured. Finally move the group resource you have configured to the other node in the cluster and begin the procedure again from step 1. A final note: All nodes in the cluster should have identical Tivoli Storage FlashCopy Manager options file. For the backup-archive client dsm.opt file, each node in the cluster can use its own nodename, but everything else in the options file should be identical. The steps that follow are only required if you have additional cluster resource groups that you want to configure with its own configuration files.
  8. From the same Windows command prompt, make a copy of the Tivoli Storage FlashCopy Manager options file (dsm.opt) and also the configuration file (fcmcfg.xml). You can issue the following commands: copy dsm.opt dsm_XXX.opt and copy fcmcfg.xml fcmcfg_XXX.xml where XXX is the nth time that you are running this step. Start with 2 and increment by one each time this step is completed. Alternatively, you can use a more descriptive name for your options and configuration files, for example, fcmappxyz.opt/fcmappxyz.cfg, ensuring the names are unique per cluster group resource configuration and ensuring the files always have the extensions *.opt and *.cfg, respectively.
  9. Using Notepad, open the newly created Tivoli Storage FlashCopy Manager options file from step 8 and make the following changes:
    1. Change the nodename option to something different. For example, NODename CLUSTER_XXX_FS where XXX is the nth time this step is completed. Start with 2, and increment by one each time this step is completed.
    2. Change the HTTPPORT option to a different available port. For example: HTTPport 1582
    3. (Standalone Configuration only) Change the VSSALTSTAGINGDIR option to the VSS staging directory volume belonging to the cluster resource group that you want to configure. For example, if the K: drive belongs to the cluster group that you want to configure, your option looks like this: VSSALTSTAGINGDIR K:\vssaltstagingdir
    4. Save and close the options file.
  10. Using Notepad, open the newly created Tivoli Storage FlashCopy Manager configuration file from step 8 and make the following changes:
    1. Look for the following HTML tag: LOCALDSMAgentnode The following example is provided:
      <LOCALDSMAgentnode>OTHELLO</LOCALDSMAgentnode>
      Change the value for the tag to something different. For example, change it to the following text:
      <LOCALDSMAgentnode>OTHELLO_XXX</LOCALDSMAgentnode>
      where XXX is the nth time that this step is completed. Start with 2, and increment by one each time this step is completed.
    2. Save and close the configuration file.
  11. Using the same Windows command prompt, change directories to the backup-archive client installation directory. Default location: C:\Program Files\Tivoli\tsm\baclient

    Make a copy of the dsm.opt file. You can issue the following command: copy dsm.opt dsm_XXX.opt where XXX is the nth time that you are completing this step. Start with 2, and increment by one each time this step is completed. Alternatively, you can use a more meaningful name depending on the resource group that you are configuring.

  12. Using Notepad, open the newly created backup-archive client options file from step 11 and make the following changes:
    1. Change the nodename option to the same value you used for LOCALDSMAgentnode in step 10. For example: NODename OTHELLO_XXX
    2. Change the HTTPPORT option. The value should be identical to the value used in step 9. For example: HTTPport 1582
    3. Change the VSSALTSTAGINGDIR option. The value should be identical to the value used in step 9. For example: VSSALTSTAGINGDIR K:\vssaltstagingdir
    4. Save and close the configuration file.
  13. If you are configuring Tivoli Storage FlashCopy Manager Standalone Configuration, skip to step 14. Otherwise, using the administrative command line dsmadmc from the Windows command line, log on to your Tivoli Storage Manager server and register the new nodes defined in the new options files. For example, run the following set of commands:
    reg node cluster_XXX_fs cluster_XXX_fs Domain=...
    reg node othello_XXX othello_XXX Domain=...
    grant proxy target=cluster_XXX_fs agent=othello_XXX
    Exit the administrative command line.
    To connect to the Tivoli Storage Manager server, issue the following command:
    dsmc -optfile="c:\Program Files\Tivoli\tsm\baclient\dsm_XXX.opt"
    You might need to provide your user ID and password for the backup-archive client DSMAGENT node to save the password on the registry. Exit the dsmc.
    To connect to the Tivoli Storage Manager server using the Tivoli Storage FlashCopy Manager node, issue the following command:
    dsmc -optfile="c:\Program Files\Tivoli\FlashCopyManager\dsm_XXX.opt"
    You might need to provide your user ID and password for the Tivoli Storage FlashCopy Manager node to save the password on the registry. Exit the dsmc.
  14. Issue the following dsmcutil commands to register the new CAD and AGENT services for this new configuration, where XXX is the nth time that this step is completed, starting with 2, and increment by one.
    dsmcutil install cad /name:"TSM Client Acceptor XXX" /node:othello_XXX 
    	/password:othello_XXX 
    	/optfile:"c:\program files\tivoli\tsm\baclient\dsm_XXX.opt" 
    	/httpport:value_from_step_9
    dsmcutil install remoteagent /name:"TSM Remote Client Agent XXX" 
    	/node:othello_XXX /password:othello_XXX 
    	/optfile:"c:\program files\tivoli\tsm\baclient\dsm_XXX.opt" 
    	/partnername:"TSM Client Acceptor XXX"
  15. If this is the first cluster node that you are configuring, open the Microsoft Failover Cluster Manager. Go to the cluster resource group that you are configuring. Right click on the resource group and select Add a resource > Generic Service. From the New Resource Wizard dialog window that is displayed, select the CAD service, named TSM Client Acceptor XXX, and continue the wizard until it is finished. Bring the TSM Client Acceptor XXX service resource online from the Microsoft Failover Cluster Manager. If you are repeating this procedure for another cluster node, the TSM Client Acceptor XXX service resource has already been configured. Go to the resource group and bring up the service resource online.
  16. Change directories to the Tivoli Storage FlashCopy Manager installation directory. Default location: C:\Program Files\Tivoli\FlashCopyManager
    Enter the following command:
    fcmcli q component /fcmoptfile=dsm_XXX.opt /configfile=fcmcfg_XXX.xml
    A list of all available volumes for backup is displayed.
  17. You have configured another group resource. If you have more resource groups to configure, repeat steps 8 through 17. Otherwise, you are ready to complete the same procedure on the other nodes in your cluster. Before you begin the procedure again on other nodes in the cluster. You must first stop, if running, all of the TSM Remote Client Agent services created in this procedure. Go to the Windows Services MMC and stop all of these services. Then, using the Microsoft Failover Cluster Manager, make all of the TSM Client Acceptor services offline from all the different resource groups configured. Finally, move each one of the group resources you have configured to the other node in the cluster and begin the procedure again from step 1. A final note: All nodes in the cluster should have identical Tivoli Storage FlashCopy Manager options files. All dsm_XXX.opt and fcmcfg_XXX.cfg files must be identical in all nodes in the cluster. For the backup-archive client dsm_XXX.opt file, each node in the cluster can use its own node name, but everything else in the options file should be identical.