Ya, I was scared reading that.
-----Original Message----- From: Joe L. Casale [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 6: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
