Bob, when you schedule the backup on the TSM server what action are you scheduling? I know with the Exchange TDP it must be COMMAND and you must have a batch file on the Exchange server that actually does the backup.
Mark -----Original Message----- From: Bob Booth - UIUC [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 1:37 PM To: [EMAIL PROTECTED] Subject: MS SQL TDP help I am hoping someone can give some insight into problems I am having getting the MS SQL TDP V2 to run on a Windows 2K box. The main problem I am having is with the scheduler. The box runs both normal backups, and TDP backups via a scheduler service. The TDP options file lists a separate port '1502' for the TCPclientport, and the box is listening on both 1501 (normal) and 1502 (TDP) in it's netstat listing. The TDP options file also lists a different node name for the TDP backup. The problem is, that the scheduler performs both backups, but the one that is supposed to be a TDP backup, remains a regular windows backup. It does not backup the database, but the same windows files that the regular ba client performs. I am a TDP newbie, and I don't do windows, so I am kind of at a loss as to where to start on this one. We have tried removing the node, the schedule, and starting over. If you run the backup by hand, the system lists the node as a TDP type client, but once the schedule runs, it reverts back to WinNT, and backs up C$ and D$. The client does not seem to be invoking the TDP module for this schedule, but we can't figure out why. The server is AIX V4.3.3 running TSM 4.1.5. Thanks for any assistance. Bob Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
