You can install TSM locally on each node of a Microsoft Cluster Server (MSCS) environment cluster. You can also install and configure the TSM 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 containing 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 move (or fail) 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.
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
You can edit your dsm.opt file on each local node to process local disk drives using the following options:
You can configure the TSM Backup-Archive Scheduler Service to back up the local cluster nodes.
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 back up.
Use the Cluster Administrator program to determine which groups contain physical disk resources for TSM to process. Register a unique node name 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 node names: 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>
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:
mscs-cluster-group-a
See Nodename for more information about this option.
q: r:
See Domain for more information about this option.
Configure a TSM Backup-Archive Scheduler Service for each cluster group using the TSM Client Service Configuration Utility, dsmcutil. Do not use the scheduler setup wizard to configure scheduler services in a MSCS environment.
Each service must have a unique name and be available for failover (moved to the other nodes in the cluster).
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:nodepassword /validate:yes /autostart:yes /startnow:yes /clusternode:yes /clustername:mscs-cluster
This installs 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.
To add a Generic Service resource to each cluster group managed by TSM use the Cluster Administrator, as follows:
TSM SCHEDULE SERVICE for GROUP-A
SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\ mscs-cluster-group-a\servername
Repeat this procedure for each cluster group managed by TSM.
To use the TSM Web client in a MSCS environment, you must configure the native TSM client to run in a MSCS environment. See "Installing the TSM Backup-Archive Client" for detailed information about installing and configuring the native TSM client in a MSCS environment.
After installing and configuring the native TSM client in a MSCS environment, perform the following steps.
Please perform the steps under Step 1 of "Configuring TSM Backup-Archive Client To Process Cluster Disk Resources".
Please perform the steps under Step 2 of "Configuring TSM Backup-Archive Client To Process Cluster Disk Resources".
In addition, specify the following option in the dsm.opt file for each cluster group:
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: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"
For more information about dsmcutil commands and options, see "Using the Dsmcutil Command".
After installing the client acceptor service and client agent, generate a password file for the node name. For example, using the values from above, issue the command:
dsmc query session -optfile="q:\tsm\dsm.opt"
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.
Add a network name and IP address resource for each group that is managed by the TSM client, using the cluster administrator.
To add an IP Address resource to each cluster group managed by TSM use the Cluster Administrator, as follows:
IP address for GROUP-A
To add a network name resource to each cluster group managed by TSM use the Cluster Administrator, as follows:
Network Name for GROUP-A
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 TSM.
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.