![]() |
![]() |
After installing and configuring the native client in a MSCS environment, perform the following steps.
Please perform the steps under Step 1 of Configuring the Backup-Archive Client to Process Cluster Disk Resources.
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:
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
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.
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:
IP address for GROUP-A
To add a network name resource to each cluster group managed by Tivoli Storage Manager, 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 Tivoli Storage Manager.
To add a Generic Service resource to each cluster group managed by Tivoli Storage Manager, use the Cluster Administrator as follows:
TSM CLIENT ACCEPTOR SERVICE for GROUP-A
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
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.
dsmc query session -optfile="q:\tsm\dsm.opt"
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.