Any update on this?
From: [email protected] To: [email protected] Subject: RE: [Exchange] Transaction logs growing like crazy Date: Thu, 5 Jun 2014 20:55:18 +0000 It looks like that DAG backup completed at 2:48am, and transaction logs went crazy after 2:59am. I wonder if backup has something to do with that. Backup is done by Symantec Backup Exec. Rami From: [email protected] [mailto:[email protected]] On Behalf Of Rami SIK Sent: Thursday, June 05, 2014 1:47 PM To: '[email protected]' Subject: RE: [Exchange] Transaction logs growing like crazy Yes, it is in DAG Rami From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, June 05, 2014 1:18 PM To: [email protected] Subject: RE: [Exchange] Transaction logs growing like crazy is this a DAG From: [email protected] To: [email protected] Subject: RE: [Exchange] Transaction logs growing like crazy Date: Thu, 5 Jun 2014 19:17:32 +0000 No exports done today. I have 60,000+ transaction log files in my log drive, and it keeps growing. I will try MS support. Rami From: [email protected] [mailto:[email protected]] On Behalf Of Tony Patton Sent: Thursday, June 05, 2014 11:33 AM To: Exchange List Subject: Re: [Exchange] Transaction logs growing like crazy Anyone running a mailbox export from a RSG to a mailbox on that DB? We had that happen earlier today, the log drive alerted for space issues, when it shouldn't have. Used 10GB in an hour. Tony On 5 Jun 2014 19:10, "Rami SIK" <[email protected]> wrote: Hi All, I just noticed that the transaction logs for one of my Exchange DBs are growing like crazy today. The server is Windows 2008 R2 running Exchange 2013 CU3 (no SP1 yet). I googled the issue, and found that ExMon would give us some insight, but I could not get in run on my Exchange 2013 server. We also use mainly Blackberry smart phones, and some using BES10 and some using BES5. Any Idea would be appreciated. Regards, Rami If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
