Hi Rajesh, Maybe it's because TDP Exchange doesn't give the information to TSM. We have studied this for our own needs and finally abandoned. Syntax used by this TDP is always changing and sometimes incoherent. For SQL, the problem is different. It's an IBM product. In the same way, backint doesn't speak no longer to TSM (since a recent version). If somebody has informations about these things ... Best regards
Christian Bagard [EMAIL PROTECTED] SOS-Restore - 32 cours Mirabeau - 13100 Aix-en-Provence - France From: "Rajesh Oak" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 20, 2004 1:39 PM Subject: Re: TSM Operational Reporting - some answers... > The Operational Reporting seems to be working fine at my site. > The only flaw is in the report for the Exchange Backup. > Since we execute a batch file which kicks off the Exchange backup, the client > summary shows successful everytime the batch file is executed successfully. After > that it has no idea if the actual backup fails. Wierd thing is for SQL backups we do > the same thing but it looks for errors in the actual SQL backups and reports it in > the client schedule summary. > Hope this is fixed ASAP because now I have to run a script which looks for the > Exchange backup seperately. > > > Rajesh Oak > Blue Cross Blue Shield of Michigan > --
