Hi, we had a "sort of the same problem", Update TSM BAclient from Version 3.7 -> 4.2.1.32, TDP 1.1.2 (before and after), after the upgrade we got the message 'Unknown format' when trying to retrive backups from the Node filespace, TSM support couldn't help there. So we had to start from scratch, renaming the node and beginnig a new backup cycle. An audit db fix=yes detail=yes found a lot of errors, but didn't resolve our problem. Environment was NT4.0, Domino 5.08.
Mit freundlichen Grüßen / Best Regards Markus Veit _________________________________________ Bayer AG IM-CTS-PSO-SBB Leverkusen, W 5 Tel.: +49(0)214/30-71254 Fax: +49(0)214/30-9671254 E-Mail: [EMAIL PROTECTED] Internet : http://www.bayer-ag.de An: [EMAIL PROTECTED] Kopie: Thema: Re: TDP for Domino backup (new) issues..... [EMAIL PROTECTED] U Received : 30.07.2002 14:39 Bitte antworten an "ADSM: Dist Stor Manager" Can't see how this could be. This is the first time the TDP and TSM client have been installed on these boxes. This is a brand new TSM AIX server (5.1.1) The owner of these boxes installed the clients she received on a CD set. I told her to upgrade the main client to 5.1.1. The TDP hasn't changed for quite a while......1.1.2 IIRC. ---------------------------------------------------------------------------------------------------- Zoltan Forray Virginia Commonwealth University - University Computing Center e-mail: [EMAIL PROTECTED] - voice: 804-828-4807 Del Hoobler <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/29/2002 07:23 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: TDP for Domino backup (new) issues..... > 07/26/2002 08:09:16 cuGetBackQryResp: Unknown objInfo header > format:8,,\CSRV50.NTF.DATA > > Any idea what these are and how to resolve them ? > > As far as I can tell, we are running the latest and greatest > client/api/TDP (I checked and there haven't been any updates for a while). Zoltan, This looks like some backups were made to this node with a higher level version of the TSM API or BA client. I would make sure that you have the lastest version of the TSM API installed and retry your operation. If it still fails the same way, I recommend that you call TSM support. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
