Jeff

You should have separate scheduler's installed to back up the local disks and
the shared disks.

The scheduler that is installed to back up the shared disks should have two
values stored in the registry:
HKLM\System\CurrentControlSet\Services\<SchedulerName>\Parameters\ClusterNode :
REG_SZ : 1
HKLM\System\CurrentControlSet\Services\<SchedulerName>\Parameters\ClusterGroupName

: REG_SZ : NameOfCluster

For the scheduler installed to back up the local disks, these values should be
absent (or have a ClusterNode value of 0).

It sounds like you might have the ClusterNode value set to 1 for the scheduler
in question, but are missing the ClusterGroupName key.

If this is the case, try using DSMCUTIL to remove the scheduler and re-install
it with the /CLUSTERNODE:YES and /CLUSTERNAME:NameOfCluster. If it's the
scheduler installed to back up the local disks, specify /CLUSTERNODE:NO.

Please be aware that I've never succeeded in getting the 4.1.2 client to work in
an MSCS environment. There is an open APAR with Tivoli that I'm waiting to be
fixed - APAR IC29377. Until this is fixed, I will continue to use 4.1.1.

Neil Schofield




The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682