Re: TSM on W2K Cluster with TDP for SQL

Geirr,

Verify that you have CLUSTERNODE YES in the
options file that runs the scheduler.

Verify that the generated password is stored
correctly on both nodes of the cluster, i.e. you can
issue a command from either node in the cluster that
it will connect and authenticate correctly with
the TSM Server.

Did you set up the registry replication for the
resource that runs the scheduler service?
That makes sure that the generated password that
is stored in the registry is replicated to the
alternate node in the cluster in the event of a failover.

If that doesn't help, you may want to look more
closely at the error logs and find out
specifically why it isn't starting up and then
call IBM service to help diagnose.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Never cut what can be untied.
- Commit yourself to constant improvement.

=================================================================

> I'm having a problem with a scheduler for TDP for SQL v. 2.2.0.1, on a MS
> Cluster. I installed it several months ago, and it has been running good
for
> all this time. Now I have a situation where the cluster resource for the
> scheduler service can't start the service. It tries 3 times, and then
fails.
> I can start the service manually, and then bring the cluster resource
> online, and it runs fine. But when a failover occurs, it fails again.
>
> The cluster is Active/Passive.
> BA Client v. 4.2.1.32
>
> On this cluster are a few other resources for the regular backup client
(for
> different cluster disks), which were installed in the same way, but these
> have no problems.
> I believed it to be a force of the tsm password for the client, but after
> checking (and updating) this is not the case.