Manual Cluster Configuration Steps

Answer

These steps are provided as a work around only if the configuration wizard fails. Please first try using the wizard to configure the server in your cluster.

Note: These steps should be run as a domain user.

1. Configure windows 2008 R2, enable mscs cluster and disk resources under a resource group for the server. You will also need a dedicated IP address and corresponding DNS entry for the server itself. This should be separate from any other IP you have previously.

2. Install the Tivoli Storage Manager server package on all cluster nodes

3. Create a server instance on all cluster nodes.

The instance directory stores the following files for the server instance:
* The server options file, dsmserv.opt
* The server key database file, cert.kdb, and the .arm files (used by clients and
other servers to import the Secure Sockets Layer certificates of the server)
* Device configuration file, if the DEVCONFIG server option does not specify
a fully qualified name
* Volume history file, if the VOLUMEHISTORY server option does not specify
a fully qualified name
* Volumes for DEVTYPE=FILE storage pools, if the directory for the device
class is not fully specified, or not fully qualified
* User exits
* Trace output (if not fully qualified)

a) Create a Tivoli Storage Manager instance, using the db2icrt command. Enter the following command on one line. The user account that you specify becomes the user ID that owns the Version 6.3 or later server (the instance user ID).

db2icrt -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is Server1, enter the following command:

db2icrt -u tsminst1 server1

You are prompted for the password for user ID tsminst1. Later, when you create and format the database, you use the instance name that you specified with this command, with the -k option.

b) Change the default path for the database to be the drive where the instance directory for the server is located. Complete the following steps:

a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command Line Tools > Command Line Processor.

b. Enter quit to exit the command-line processor.

A window with a command prompt should now be open, with the environment
properly set up to successfully issue the commands in the next steps.

c. From the command prompt in that window, issue the following command to set
the environment variable for the server instance that you are working with:

set db2instance=instance_name


The instance_name is the same as the instance name that you specified when you
issued the db2icrt command. For example, to set the environment variable for the
Server1 server instance, issue the following command:

set db2instance=server1

d. Issue the command to set the default drive:

db2 update dbm cfg using dftdbpath instance_location

For example, the instance directory is d:\tsm\server1 and the instance location is
drive d:. Enter the command:

db2 update dbm cfg using dftdbpath d:

e. Set the DB2 code page by issuing the following command

db2set -i instance_name DB2CODEPAGE=819

The instance_name is the same as the instance name that you specified when you
issued the db2icrt command. For example, to set the environment variable for the
Server1 server instance, issue the following command:

db2set -i server1 DB2CODEPAGE=819

c) Create a new server options file. See Configuring server and client communications.

4. On each node do the following steps:

a) cd /d c:\windows\cluster
b) regsvr32.exe /s /u TsmSvrRscExX64.dll
c) cluster resourcetype "TSM Server" /delete
d) copy ...\program files\tivoli\tsm\console\TsmSvrRscX64.dll c:\windows\cluster
e) copy ...\program files\tivoli\tsm\console\TsmSvrRscExX64.dll c:\windows\cluster
f) regsvr32.exe /s TsmSvrRscExX64.dll
g) Create the TSM server service by issuing the following command:

sc create "service_name" binPath= "path_to_server_dir\dsmsvc.exe -k instance_name" start= demand obj= "domain\user" password= password

For example, if the instance name was Server1 and dsmsvc.exe was in d:\program files\tivoli\tsm\server, and the domain user was test\tsminst1 with a password of passw0rd, the following would be used.

sc create "TSM Server1" binPath= "d:\program files\tivoli\tsm\server\dsmsvc.exe -k SERVER1" start= demand obj= "test\tsminst1" password= passw0rd


5. On the primary Node only, issue:

a) Run db2mscs. For example:

db2mscs -f:<config file>

db2mscs.config is created by the wizard in the server instance working directory.
Its contents will look something like this:

DB2_INSTANCE=<instance>
CLUSTER_NAME=<cluster name>
GROUP_NAME=<group name>
DB2_LOGON_USERNAME=<domain user>
DISK_NAME=<shared disk>
note: repeat DISK_NAME line for each disk that is in the resource group. Make sure the one containing the TSM server instance directory is first
...
IP_NAME=<ip name - can be anything>
IP_ADDRESS=<ip address for the TSM server>
IP_SUBNET=<subnet mask>
NETNAME_NAME=<network name - can be anything>
NETNAME_VALUE=<actual DNS name that corresponds with the IP address>
NETNAME_DEPENDENCY=<the value of IP_NAME specified above>
IP_NETWORK=<shared network name>

For example:

DB2_INSTANCE=SERVER1
CLUSTER_NAME=tempestcluster
GROUP_NAME=TSM Server1 Group
DB2_LOGON_USERNAME=tsmdev2\tempestgrp
DISK_NAME=Cluster Disk 1
IP_NAME=TSM SERVER1 Group IP ADDRESS
IP_ADDRESS=9.11.142.188
IP_SUBNET=255.255.255.0
NETNAME_NAME=TSM SERVER1 Group Network Name
NETNAME_VALUE=tempestsrv1
NETNAME_DEPENDENCY=TSM SERVER1 Group IP ADDRESS
IP_NETWORK=Cluster Network 1


6. Stop the db2 resource with the following command:

cluster resource instance_name /offline

For example, if the instance name is Server1 you would issue the following command.

cluster resource SERVER1 /offline


7. If setting up a new instance, now would be the time you formatted the TSM server database. To do this, you would use the following command from the instance directory.

dsmserv -k instance_name format dbdir=db_dir activelogsize=active_log_size
activelogdirectory=active_log_dir archlogdirectory=archive_log_dir
archfailoverlogdirectory=archive_failover_dir
mirrorlogdirectory=mirror_log_dir

For example:

dsmserv -k server1 format dbdir=d:\tsm\db001 activelogsize=8192
activelogdirectory=e:\tsm\activelog archlogdirectory=f:\tsm\archlog
archfailoverlogdirectory=g:\tsm\archfaillog
mirrorlogdirectory=h:\tsm\mirrorlog

Additional information about this command can be found in the manual under
DSMSERV FORMAT.


8. Export the registry key and import it on all secondary nodes

For example, if your instance name was server1, the key would be

HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1

9. Issue the following commands to create the TSM server resource

cluster resourcetype "TSM Server" /create /DLL:tsmsvrrscX64.dll /type:"TSM Server"
cluster /regadminext:"c:\windows\cluster\tsmsvrrscexX64.dll"
cluster resource "TSM SERVER1 Server" /create /group:”TSM_group_resource” /type:"TSM Server"
cluster resource "TSM SERVER1 Server" /adddep:"network_resource"
cluster resource "TSM SERVER1 Server" /adddep:"DB2_resource"

For example:

cluster resourcetype "TSM Server" /create /DLL:tsmsvrrscX64.dll /type:"TSM Server"
cluster /regadminext:"c:\windows\cluster\tsmsvrrscexX64.dll"
cluster resource "TSM SERVER1 Server" /create /group:”TSM Server1 Group ” /type:"TSM Server"
cluster resource "TSM SERVER1 Server" /adddep:"tempestsrv1"
cluster resource "TSM SERVER1 Server" /adddep:"SERVER1"

10. Add dependencies for each shared disk resource, starting with the disk where the instance is found:

cluster resource "TSM SERVER1 Server" /adddep:"disk_name"
cluster resource "TSM SERVER1 Server" /adddep:"disk_name"
….. repeat for all shared disk resources

11. Issue the following to set the location for the console log. This log is useful to review in case the TSM server resource does not come online.

cluster resource "TSM SERVER1 Server" /privprop service="TSM Server1" ServerKey="SERVER1" ConsoleLogFile="<instance_path>\console.log" LogToFile=1

12. Run dsmsutil on all nodes including the primary node to set the
$$_TSMDBMGR_$$ password.

For example:

"c:\program files\tivoli\tsm\server\dsmsutil.exe"
UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO /OPTFILE:
"d:\tsmserver1\tsmdbmgr.opt"

13. Bring the cluster resource online with the following command.

cluster resource "TSM SERVER1 Server" /online


You can now log into the server and issue commands to verify that it is operational.