DEL, Thanks, Actually the 2 nodes that were in trouble are running 2.2.0.1 and were in a Cluster configuration. Tony had the Clustername in the dsm.opt file. But we can run manual backups using TDPSQLC commands after changing it to the Virtual nodename of the Sqlserver server, we can not run his script after the change(Receives of these erors - ACO0302E -- NODENAME cannot be the local machine name when CLUSTERNODE is set to YES). I believe he has open support on this issue.
Regards, Bruce -----Original Message----- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 2:14 PM To: [EMAIL PROTECTED] Subject: Re: TDP For SQL 2.2 password errors Bruce, Are you sure you are using the correct NODENAME for TDP for SQL vs. the NODENAME for the base client? Go to the TDP for SQL installation directory, and use the command-line client to issue: tdpsqlc query tsm /tsmpassword=xxxxx If that doesn't work, and you get the same error, then reset the password on the TSM server and try again. If it still doesn't work, please call support. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Leave everything a little better than you found it. - Smile a lot: it costs nothing and is beyond price. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________ ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
