Del,
I fixed this in the following way:
1. Two services need to be installed on each node of the Cluster with
the batch file; dsmcutil install /machine:%1 /name:"%2 TSM Agent"
/node:"SQL_%2" /password:"SQL_%2" /optfile:%3:\tsm\msSQL\dsm.opt
/clientdir:C:\tsm\BACLIENT /clusternode:yes /clustername:<clustername>
/autostart:no
a. Install the first service on Node 1 using the parameters
<machine_name_1> <Virtual_Sql_Name_1> <shared_disk_resource_name_1>
b. Fail all Node 2 resources over to Node 1
c. Install the second service on Node 1 using parameters
<machine_name_1> <Virtual_Sql_Name_2> <shared_disk_resource_name_2>
d. Fail Node 2 resources back to Node 2
e. Install the first service on Node 2 using the parameters
<machine_name_2> <Virtual_Sql_Name_2> <shared_disk_resource_name_2>
f. Fail all Node 1 resources over to Node 2
g. Install the second service on Node 2 using parameters
<machine_name_2> <Virtual_Sql_Name_1> <shared_disk_resource_name_1>
2. The result is that each node is running both of these two services,
both set to manual.
a. <Virtual_Sql_Name_1> TSM Agent
b. <Virtual_Sql_Name_2> TSM Agent
3. Now, when the nodes fail over, the service restarts and any
scheduled event that is still within the window will restart.
I've been unable to find this documented anywhere in the TSM literature, or,
if it's there, it's not clear that both services are required on both nodes.
Glen
-----Original Message-----
From: Del Hoobler [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 1:45 PM
To: [EMAIL PROTECTED]
Subject: Re: TDPS in a cluster
Glen,
A few suggestions... The steps to run in a cluster are
quite "touchy". If you miss a step or a step does not
complete, or is done out of order, things may not work.
A few things to check:
1.) Make sure you are using CLUSTERNODE YES in the options file
2.) Make sure you are running the same level of TSM API and
TSM scheduler on both sides of the cluster.
(Hopefully, you are running at least 4.1.2)
3.) Make sure the scheduler services are set up
**exactly** identical on both nodes.
4.) Check the Event Log for any message that might help.
Check the dsmerror.log and dsierror.log.
Keep in mind, if the scheduler is failing to start,
TDP for SQL has not even been invoked yet...
...so the problem has to do with the scheduler
service not being able to "start".
If you still cannot get it solved, call IBM support and
**insist** on speaking with TSM level 2.
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
"It's a beautiful day. Don't let it get away." -- Bono
Glen Churchfield
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
ATE.OH.US> cc:
Sent by: "ADSM: Subject: TDPS in a cluster
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>
06/20/2001 01:11
PM
Please respond
to "ADSM: Dist
Stor Manager"
I have a pair of Win2K servers clustered with MSCS and running MSSQL 7.0.
Backups run fine with TDP 2.2, but if either node fails over to the other
node, the "failed-from" TSM schedule service fails to start on the new box.
When it fails back, the services start and run fine. The setup was
according
to the TDP V2.2 Installation and User's Guide which includes duplicate
options files and config files in the startup directory and replicated
registry keys for the passwords. Has anyone solved this problem? Tivoli
level 1 support was clueless after 2.5 hours on the phone. I'm hopeful that
I've missed something that someone on the list has seen.
Glen Churchfield
Frontway TSM Consultant
Columbus, Ohio
[EMAIL PROTECTED]
740-503-3384
