Hi GuysI have deleted a public folder of 14GB in exchange system manager on a 2003 exchange server. Now the server is writing log after log and has nearly filled a 40 GB drive. can this be possible. What can do to fix this as it amd worried this will bringdown all my public folders? Is this a normal process.Please helpThanks

Hi,Did you run a full backup after it ? This should flush the log filesRegards,Johanblog: www.johanveldhuis.nl

Hi JohanI have not run a full back up yet, that should run in the next hour or two. The issue that i have is that the exchange is now writing 160MB of log files a minute and its filling up the drive so fast. Do you think a full back will stop the logging?

Did you check below article? This will help you to troubleshoot the problem at various levels... Troubleshooting Fast Growing Transaction Logs on Microsoft Exchange 2000 Server and Exchange Server 2003 http://technet.microsoft.com/en-us/library/aa996191(EXCHG.65).aspxAmit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hows the issue currently? Whats the result of backup?

Hi GuysThanks for your repliesIt seems that due to the size of the folders deleted, exchange hadto log all the info that wasbeing deleted incaseit had to roll back. It caused thelogs of about 160MB a minute and continued like this for about 5 hours. It finally stopped after all the data was cleared out of the folderswith logs of about 64 GB. The issue with running a full backup during this time was a good idea but the load generated by deleting the folders could have caused a lot moreissues performance wise on exchange at the time.I think the lesson learnedhere is that it is best to manually delete the emails in the public folder first before deleting the folder in the exchange system manager. Also I think itagood ideato limit the sizeof the folders so that they don't grow as large as mind did. This is not a good idea as you will end up with a folder that is not accessible and that you will have to delete through ESM and it will generate a large amount of Logs.A full back has been run and the 64 GB of logs have been removed!Thanks for your replies and I hope youcan learn from my mistakes. I for one am going to start to implement stricter policies on my exchange server from now on.

O, I see. Glad you solved the issue eventually, and thanks for sharing your experience at here, which would really help more people Thanks! J