Hi, I think the problem was the exchange it self. Every morning, the exchange service take a big resource memory (about 8 GIgs), so we're still waiting for the exchange guy to solve that problem. One more thing, after a full or incremental backup, what's happening to the exchange log? Is it directly deleted, or it will deleted after a cycle log? Does anyone have experinces on this?
Best Regards, Yudi Darmadi PT Niagaprima Paramitra Jl. KH Ahmad Dahlan No.25 Kebayoran Baru, Jakarta Selatan 12130 Phone: 021-72799949; Fax: 021-72799950; Mobile: 081905530830 http://www.niagaprima.com ----- Original Message ----- From: "Tchuise, Bertaut" <btchu...@lmus.leggmason.com> To: <ADSM-L@VM.MARIST.EDU> Sent: Wednesday, July 22, 2009 7:46 PM Subject: Re: [ADSM-L] TDP Exchange Error Yudi, Did you see any outstanding error messages from Exchange in the event viewer? Did you get additional information from the logs in the TDPExch directory? "tdpexcc q exchange" showed that circular logging was disabled; so TDP shouldn't be assuming otherwise. You may want to work on this issue with your exchange admin before restarting the exchange server. If non-conclusive, enable tracing, run a manual full then incr or diff backup, provide the trace to IBM for further investigation. Please Yudi, let us know once you find out what caused your issue. BERTAUT TCHUISE Storage Support Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Yudi Darmadi Sent: Tuesday, July 21, 2009 9:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP Exchange Error I'm using legacy backup, and From The "tdpexcc q exchange" command, all circular logging are disabled. It seems that when backup occured, tdp exchange still asume the circular logging were enabled. Do i have to stop & restart the exchange server? Best Regards, Yudi Darmadi ----- Original Message ----- From: "Tchuise, Bertaut" <btchu...@lmus.leggmason.com> To: <ADSM-L@VM.MARIST.EDU> Sent: Wednesday, July 22, 2009 12:42 AM Subject: Re: [ADSM-L] TDP Exchange Error Yudi, After the legacy and VSS full backups, the exchange server deletes the logs; the logs won't be deleted if the storage groups are not mounted. Similarly during the legacy incremental backups, the exchange server deletes the transactional logs after they are being backed up. Using the command line, run "tdpexcc query exchange" to ensure that the circular logging is effectively disabled on the exchange server and check the event viewer. BERTAUT TCHUISE Storage Support Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Yudi Darmadi Dear TSM-ers, I need help for my Exchange Backup. I got this message when performing an incremental Backup: *ACN5798E MS Exchange API HRESEBACKUPSETUP() failed with HRESULT: 0xc800020e -An incremental backup cannot be performed when circular logging is enabled. *ACN5798E MS Exchange API HRESEBACKUPOPENFILE() failed with HRESULT: 0xc8000232 -Some log or patch files are missing. But The Circular logging for all Storage Groups had already disabled. There's no problem when performing Full Backup, but the logs weren't deleted. Does a full backup straight automatically delete those logs? IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
