Tivoli Header

Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide

Configuring the Web Client To Process Cluster Disk Resources

After installing and configuring the native client in a MSCS environment, perform the following steps.

Step 1: Identify the Cluster Groups to Manage

Please perform the steps under Step 1 of Configuring the Backup-Archive Client to Process Cluster Disk Resources.

Step 2: Configure the Client Options File

Please perform the steps under Step 2 of Configuring the Backup-Archive Client to Process Cluster Disk Resources.

In addition, specify the following option in the dsm.opt file for each cluster group:

httpport
Specify a unique TCP/IP port number that the web client uses to communicate with the client acceptor service associated with the cluster group. See Httpport for more information about this option.
Note:
It is preferrable to specify a different log name using the schedlogname option in the dsm.opt file for each cluster group.

Step 3: Install a Client Acceptor Service and Client Agent

Install a unique client acceptor service and client agent for each cluster group and generate a password file.

To install the Client Acceptor Service for group-a from machine node-1, ensure that node-1 currently owns group-a and issue the following command:

   dsmcutil install cad /name:"tsm client acceptor: group-a"
   /optfile:q:\tsm\dsm.opt /node:mscs-cluster-group-a
   /password:nodepassword /autostart:yes

This will install the service on node-1.

To install the Client Agent Service for group-a from machine node-1, ensure that node-1 currently owns group-a and issue the following command:

   dsmcutil install remoteagent /name:"tsm client agent: group-a"
   /optfile:q:\tsm\dsm.opt /node:mscs-cluster-group-a
   /password:nodepassword /partnername:"tsm client acceptor: group-a"
   /clusternode:yes /clustername:mscs-cluster
Note:
Do not use the /autostart:yes option.

For more information about dsmcutil commands and options, see Using the Dsmcutil Command.

Using Cluster Administrator, move group-a to node-2. From node-2, issue the same commands above to install the services on node-2 and generate a password file. Repeat this procedure for each cluster group.

Step 4: Create a Network Name and IP Address Resource

Add a network name and IP address resource for each group that is managed by the client, using the cluster administrator.

To add an IP Address resource to each cluster group managed by Tivoli Storage Manager, use the Cluster Administrator as follows:

  1. Select the group-a folder under the MSCS-Cluster\Groups folder and select File > New> Resource from the dropdown menu.
  2. In the New Resource dialog, enter the following information:
  3. In the Possible Owner dialog, ensure that all cluster nodes appear as possible owners. Press Enter.
  4. In the Dependencies dialog add all physical disk resources as Resource Dependencies. Press Enter.
  5. In the TCP/IP Address dialog, enter appropriate values for address, subnetmask, and network. Press Enter.
  6. Select the new resource from the Cluster Administrator utility, and from the dropdown menu click File and then Bring Online.

To add a network name resource to each cluster group managed by Tivoli Storage Manager, use the Cluster Administrator as follows:

  1. Select the group-a folder under the MSCS-Cluster\Groups folder and select File > New > Resource from the dropdown menu.
  2. In the New Resource dialog, enter the following information:
  3. In the Possible Owner dialog, ensure that all cluster nodes appear as possible owners. Press Enter.
  4. In the Dependencies dialog add the IP address resource and all physical disk resources as Resource Dependencies. Press Enter.
  5. In the Network Name Parameters dialog, enter a network name for GROUP-A. Press Enter.
  6. Select the new resource from the Cluster Administrator utility, and from the dropdown menu click File and then Bring Online.

The IP address and network name to backup the disks in the cluster group are now resources in the same group.

Repeat this procedure for each cluster group managed by Tivoli Storage Manager.

Step 5: Creating A Generic Service Resource For Failover

To add a Generic Service resource to each cluster group managed by Tivoli Storage Manager, use the Cluster Administrator as follows:

  1. Select the group-a folder under the MSCS-Cluster\Groups folder and select File > New > Resource from the dropdown menu.
  2. In the New Resource dialog, enter the following information:
  3. In the Possible Owner dialog, ensure that all cluster nodes appear as possible owners. Press Enter.
  4. In the Dependencies dialog add all physical disk resources as Resource Dependencies. Press Enter.
  5. In the Generic Service Parameters dialog, enter the service name you specified with the dsmcutil command, in the Service Name field. Leave the Startup Parameters field blank. Press Enter.
  6. In the Registry Replication dialog, add the registry key corresponding to the Tivoli Storage Manager node name and server name. The format for this key is:
    SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\nodename\servername
    

    where nodename is the name of your Tivoli Storage Manager node, and servername is the name of the Tivoli Storage Manager server that the node connects to. For example, if the node name is mscs-cluster-group-a and the Tivoli Storage Manager server name is mytsmserver, then you should enter the following registry key in the Registry Replication dialog:

    SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\mscs-cluster-group-a\mytsmserver
    
    Note:
    This entry should match an existing key in the registry.

The client acceptor service is now a resource in the same group. If the group is moved (failed) to the other nodes in the cluster, the service should correctly fail over between the cluster nodes and notify both cluster nodes of automatic password changes.

Note:
If you manually change the password, you will need to stop the remote agent and the client acceptor services, regenerate the password, and restart the client acceptor service (do not restart the remote agent). You can generate the password by running this command:
dsmc query session -optfile="q:\tsm\dsm.opt"

Step 6: Start the Web Client

  1. Start the TSM Client Acceptor Service for each resource group on each node.
  2. To start the Web client, point your browser at the IP address and httpport specified for the Resource Group. For example, if you used an IP address of 9.110.158.205 and specified an httpport value of 1583, open the web address: http://9.110.158.205:1583.

Alternatively, you may point your browser at the network name and httpport. For example, if you used a network name of cluster1groupa and specified an httpport value of 1583, open the web address: http://cluster1groupa:1583.

Note that the Web client connects to whichever machine currently owns the resource group. The Web client displays all of the local file spaces on that machine, but to ensure that the files are backed up with the correct node name you should only back up the files for the resource group.

When failing back to the original node after a failover scenario, ensure that the remote agent service on the original machine is stopped. The remote agent may be stopped manually, or it will stop automatically after 20 to 25 minutes of inactivity. Because the remote agent is configured for manual startup, it will not start automatically if the machine on which it was running is rebooted.


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