Installation and User's Guide

option with dsmcutil.exe, only when installing a scheduler service for a clustergroup. Do not specify a clustername of more than 64 characters. If you specifymore than 256 characters and you are using Veritas Storage Foundation withHigh Availability or a Microsoft Cluster Server configuration, you might not beable to install or start the Tivoli Storage Manager scheduler service, and (2)/clusternode:yes - Specifies that you want to enable support for clusterresources. Use this option in the dsm.opt file for each cluster group, and withdsmcutil.exe when installing a scheduler service for a cluster group.4. Common mistakes are made in typing the syntax of the dsmcutil.exe command.An easy way to prevent such syntax problems is to create a temporary text filewhich is accessible to the cluster group (for instance, place it on a cluster drivebelonging to that cluster group), and type the syntax into this file. Whenneeded, cut and paste this syntax from the file to the DOS prompt and pressthe Enter key. It guarantees the consistency of the command syntax regardlessof which computer you enter it on.5. If the scheduler service is failing to restart after a failover of the cluster groupoccurs (using the MOVE GROUP option in Cluster Administrator, for example),there might be potential password synchronization problems between the twocluster workstations. To verify that the passwords are the same, browse to thisregistry key on each workstation and compare the encrypted password value:HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\\.If the encrypted keys for this node do not match between the two clusterworkstations, there is a password mismatch on one or both of the twoworkstations. To correct this problem, use the dsmc.exe program to update thepassword manually on both workstations.For example, assume that the Y: drive is part of the cluster group that isexperiencing problems being backed up with a scheduler service. The Y:\tsmdirectory contains the dsm.opt file for this cluster group in the Y:\tsm directory.To update the password manually, enter the following command on bothworkstations: dsmc -optfile=Y:\tsm\dsm.opt -clusternode=yes, and enter thefollowing command to receive the prompt for the node name and password:dsmc q se -optfile=Y:\tsm\dsm.opt -clusternode=yes.Verify that the passwords are synchronized, and restart the scheduler service toverify if the password remains consistent. If password mismatching continues,it might be due to a syntax error in the original dsmcutil.exe command thatwas used to install the scheduler service. In this case, uninstall the schedulerservice (using the dsmcutil remove /name: command) andreinstall the scheduler service again (using the shared text file syntax as shownpreviously).Q: How do you add a cluster drive to an existing Tivoli Storage Manager clusterscheduler service resource for backup?A: To add an additional cluster drive resource to an existing Tivoli StorageManager client cluster scheduler service, the following components must bemodified or updated to properly reflect this change:1. The cluster drive resource, and any related resource shares, must exist andreside within the designated cluster group as defined in the Microsoft ClusterAdministrator utility or VCS Configuration Editor. The designated clustergroup must already contain the cluster scheduler service resource for whichthis new drive is added.2. The dsm.opt file used by the designated cluster scheduler service resource mustbe modified to include the additional cluster drive resource on the domainChapter 2. Configure the Tivoli Storage Manager client 61