Tivoli Storage Manager Installing the Clients


Appendix F. Configuring the Backup-Archive Client in a Microsoft Cluster Server Environment

You can install TSM locally on each node of an MSCS cluster and configure the TSM Backup-Archive Scheduler Service for each cluster node to manage all local disks, and each cluster group containing physical disk resources.

For example, cluster mscs-cluster contains two nodes: node-1 and node-2, and two cluster groups which contain physical disk resources: group-a and group-b. In this case, an instance of the TSM Backup-Archive Scheduler Service should be installed for node-1, node-2, group-a, and group-b. This ensures that proper resources are available to the TSM Backup-Archive client when disks are moved (or failed) between cluster nodes.

The clusternode option ensures that TSM manages backup data logically, regardless of which cluster node backs up a cluster disk resource. Use this option for TSM nodes that process cluster disk resources, and not local resources. See Clusternode for more information.


Installing the TSM Backup-Archive Client

Install the TSM Backup-Archive client software on a local disk on each cluster node. The executables should reside in the same location on each local drive, for example:

C:\Program Files\tivoli\tsm\baclient

Configuring TSM Backup-Archive Client To Process Local Nodes

You can edit your dsm.opt file on each local node to process local disk drives, using the following options:

nodename
If a value is not specified, the local machine name is used. See Nodename for more information.

domain
If a value is not specified, all local drives that are not owned by the cluster are processed. See Domain for more information.

clusternode
Do not specify this option when processing local drives. See Clusternode for more information.

You can configure the TSM Backup-Archive Scheduler Service to backup the local cluster nodes.


Configuring TSM Backup-Archive Client To Process Cluster Disk Resources

Ensure that TSM manages each cluster group that contains physical disk resources, as a unique node. This ensures that TSM correctly manages all disk resources, regardless of which cluster node owns the resource at the time of backup.

Step 1: Identify the Cluster Groups to Manage

Use the Cluster Administrator program to determine which groups contain physical disk resources for TSM to process. Register a unique nodename on the TSM server for each group. For example, cluster mscs-cluster contains the following groups and resources:

In this example, the TSM administrator registers two nodenames: mscs-cluster-group-a and mscs-cluster-group-b. For example, to register mscs-cluster-group-a the TSM administrator can enter the following command:

  register node mscs-cluster-group-a <password>

Step 2: Configure the Client Options File

Configure the client options file dsm.opt for each cluster group. Locate the option file on one of the disk drives that are owned by the cluster group. For example, the option file for MSCS-CLUSTER-GROUP-A should reside on either Q: or R:. To configure the dsm.opt file for each cluster group, specify the following options:

nodename
Specify a unique name. For example:
  MSCS-CLUSTER-GROUP-A

See Nodename for more information about this option.

domain
Specify the drive letters for the drives which are managed by the group. For example:
  Q: R:

See Domain for more information about this option.

clusternode
Specify the Yes value. See Clusternode for more information about this option.

passwordaccess
Specify the generate value. See Passwordaccess for more information about this option.

errorlogname
Specify a unique error log name. See Errorlogname for more information about this option.

schedlogname
Specify a unique schedule log name. See Schedlogname for more information about this option.

Step 3: Configure the Scheduler Service

Configure a TSM Backup-Archive Scheduler Service for each cluster group. Each service must have a unique name and must be installed on each node of the cluster so that the service is available for failover.

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

   dsmcutil install SCHEDuler /NAME:"tsm scheduler service : group-a"
   /clientdir:c:\Program Files\tivoli\tsm\baclient /optfile:q:\tsm\
   dsm.opt /node:mscs-cluster-group-a /password:n /validate:no 
   /autostart:yes /startnow:yes

This will install the service on node-1.

Using Cluster Administrator, move group-a to node-2. From node-2, issue the same dsmcutil command above, to install the service on node-2. Repeat this procedure for each cluster group.

Step 4: Creating A Generic Service Resource For Failover

The new scheduler service should now be associated with the cluster group. This allows the service to correctly fail over between the nodes, and to manage the automatic password changes so that both nodes are notified of the new password.

A Generic Service resource should be added to each cluster group to be managed by TSM. Using the Cluster Administrator, select the group-a folder under the MSCS-Cluster\Groups folder and select File> New> Resource from the pulldown menu, and enter the following information:

  1. In the New Resource dialog, enter the following information:
  2. In the Possible Owner dialog, ensure that all cluster nodes appear as possible owners. Press Enter.
  3. In the Dependencies dialog add all physical disk resources as Resource Dependencies. Press Enter.
  4. 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.
  5. In the Registry Replication dialog, add the key corresponding to the nodename. For example:
      software\tivoli\tsm\currentversion\backupclient\nodes\
      mscs-cluster-group-a
    

    in this example MSCS-Cluster-Group-A is the nodename.

  6. Select the new resource from the Cluster Administrator utility, and select File> Bring Online from the pulldown menu.

Repeat this procedure for each cluster group to be managed by TSM.

At this point, the service to backup the disks in the cluster group is a resource in the same group; if the group is moved (failed) to the other nodes in the cluster, TSM will process the disks correctly.


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