Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk



On Dec 4, 5:38 pm, "Mark Arnold [MVP]" <m...@xxxxxxxx> wrote:
Well, nobody has explained to you why the 128MB message blasted 20
gigs of transaction logs. Sure, 128MB (plus a bit of rounding up and
bloat) per store if each store are in their own SGs but that's a
gig-and-a-bit worth of logs across the board (give or take a pinch of
salt and a chunk of rounding again)
Are we looking at some message looping going on, some anti virus
application having a total epi-fit or have you got some external
recipients and non deliveries. All that's going to ramp it up. You're
going to be pushed to get to 20 gigs of TLogs generated individually
but when everything adds together it's fair to say that stupid is as
stupid does (Lt Dann etc.)

So what you're saying is that 1 attachment gets written to the logs
per store even though the message was sent to 250 people. (as opposed
to 1 attachement per recipient)? If I have ten stores, then that's
around 1 GB of log -- not close to what I saw.

There is antivirus installed, and I know that some people had their
OOA turned on.

I saw at least a 10 GB increase in the logs, and it would have been
more if I had not temporarily enabled circular logging. I had to run
circular logging for 45 minutes before the rotation of the logs slowed
down enough for me to go back to regular logging.

Could you explain what you mean by email loop? Are you talkign about
NDR's or something more specific? Could the OOA be causing the loop?

Sorry to beat this thing to death -- just trying to understand :-) I
appreciate your replies.

Beth

.



Relevant Pages

  • Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
    ... gigs of transaction logs. ... bloat) per store if each store are in their own SGs but that's a ... salt and a chunk of rounding again) ... transaction logs for every transactions & then the database will have ...
    (microsoft.public.exchange.admin)
  • RE: SBS 2003 Premium - Midnight Crash
    ... I hope that by deleting the logs that are ... However my server did crash at 00:30 again with no obvious reason. ... raid rebuilds itself but exchange store database was damaged. ...
    (microsoft.public.windows.server.sbs)
  • Re: Logs not flushing
    ... Definitely doing a full backup each night (flush committed logs). ... Information Store NGS Storage Group: ... Information Store NGS Storage Group: Deleting log files D:\Exchange ...
    (microsoft.public.exchange.admin)
  • Re: public and private mailboxes randomly dismounting
    ... When posting logs an important piece is the Event ID and Source. ... Information Store First Storage Group: An attempt to move the file ... An error occurred while writing to the database log file of storage group ...
    (microsoft.public.windows.server.sbs)
  • Re: changing the exchange structure
    ... To answer the first question, it depends on how you do it. ... smaller store size. ... and the amount of contention for the logs remains about the same. ... If you create another storage group, and put the new store there, then you ...
    (microsoft.public.exchange.design)