Exchange wisdom once held that the logs should be on a fat partition due to the sequential access speed. Nowadays faster hardware compensates nicely so its not as important, but there are plenty of legacy servers with the old configuration.
If you lose the transaction logs the information store usually becomes inconsistent and the info store service refuses to start with a service specific error message. Nasty stuff. Sometimes you can jig it with eseutil, but that works by deleting the invalid pages and causes definite data losses. Cheers, Marty -----Original Message----- From: Joe L. Casale [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 10:27 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 I don't know what would happen, but presuming best case scenario, I would ponder a guess you did loose info and didn't know it, how would you know anyway! If a few users lost a couple of emails, it might not even hit your desk. A scary procedure, if the server was properly designed, the logs are on an ntfs partition, so I would never even attempt such a thing! Just my thoughts.. Jlc -----Original Message----- From: ONG Liang Bu (CSC) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 2:54 AM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 Sorry was occupied by meetings for the whole day. Thanks for all the expert advise. Have done these a couple of times without knowing need to check whether the transaction logs are committed. This is the first time I read abt this. Lucky I did not lost any thing in the past. -----Original Message----- From: Marty Richards [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 12:37 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 There are several, this one isn't bad. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q259751 Cheers, Marty -----Original Message----- From: Joe L. Casale [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 3:24 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 Interesting, do you know what technet article? I am curious to read its explanation. I still wouldn't do it, but just curious! jlc -----Original Message----- From: Marty Richards [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 9:06 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 They are committed - up to a point. The fun part is finding that point and not deleting past it... there are technet notes which describe how to work out where the checkpoint is, and therefore which logs can be removed. Personally though I'd take the compression and backup/flush option if available - easy and relatively safe. Is there anything else on this volume which can be moved or compressed? Cheers, Marty -----Original Message----- From: Joe L. Casale [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 I don't think that's right buddy, they aren't committed until you backup, then they are flushed. They should be an ntfs partition, a better solution is to compress a few, then back the darn thing up. If those logs aren't committed, I don't know wtf would happen if you removed them and backed up, but it sounds dangerous! Hey William... jlc -----Original Message----- From: ONG Liang Bu (CSC) [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 6:50 PM To: MS-Exchange Admin Issues Subject: RE: Transaciton logs in 5.5 Happen to me before when backup giving problems and the transaction log building up. You need to remove some log files manually. Move all log files before today. I assumed any transaction log older than today have been committed to the Information Stores. Be careful don't touch these 3 files - edb.log, res1.log, res2.log. Don't know what these is but saw it since the day Exchange is installed. -----Original Message----- From: Scott Burgin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 4:20 AM To: MS-Exchange Admin Issues Subject: Transaciton logs in 5.5 We had to turn off circular logging for Arcserver to backup exchnage a while back. Anyway, the information store won't start up because it says the transaction logs are too full. I re-enabled circular logging, but the information store still won't start. Any ideas? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
