Yiannakis,

If you are referring to the registry entries under here:

   HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\

then you can delete the entry underneath that branch
that matches your nodename. You will need to store it again
before running Data Protection for SQL from a scheduler
session by running a command like this:

   TDPSQLC QUERY TSM /TSMPassword=tsmpassword /TSMOPTFile=dsmoptfilename

make sure you are always pointing to the same option file name in
all of the commands that you run.

The Data Protection for SQL User's Guide also has a step by step
appendix section on setting up a scheduler session, including the special
considerations for a cluster environment.

One other thing to try... change the NODENAME to something
other than the SQL Server name.. for example, try FUNDTSQL_SQL
to see if it changes anything.

If you are still having problems, please call IBM Support and they
can step through it with you.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/27/2004
01:28:32 AM:

> Hi Neil,
> 1. You're probably right about the /CLUSTERNODE:YES with dsmcutil. I'll
try
> that too, even though I believe that's not the problem.
>
> 2. I didn't mention the definition of a generic service cluster resource
> because that's the next step in the manual. We did that on the previous
> cluster we had set up and it working fine. We also did this definition
on
> this cluster without testing the backup but the resource was failing,
> resulting in a loop of moving the group from node 1 to node 2 and vice
> versa. We managed to stop that from happening and then followed what the
> manual suggests, i.e. to test that the scheduler is ok by running a test
> backup step (on model db for example) just to test that it
authenticates.
> And this is where we hit the authentication failure.
>
> 3. I'll try to use your third suggestion to change FROMSQLSERVER
parameter
> in the tdpsql.cfg to FUNDTSQL.
>
> I believe that there's something wrong with the registry values. Can I
> safely delete these values using regedit or am I going to corrupt the
> registry ?
> Thanks
> Yiannakis