Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: sillz <beth.stover@xxxxxxxxx>
- Date: Thu, 6 Dec 2007 09:06:34 -0800 (PST)
On Dec 5, 11:33 am, sillz <beth.sto...@xxxxxxxxx> wrote:
On Dec 5, 11:27 am, sillz <beth.sto...@xxxxxxxxx> wrote:
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 1attachmentgets 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
I forgot to mention: There were no external recipients on this
email. Also, we do use an externally hosted anti-spam solution that
also acts as our MX record. I'm not sure how this would affect an
email loop in this case, but I though I would mention it.
People did start deleting the email which would generate more logs.- Hide quoted text -
- Show quoted text -
I think I understand this better. I got this from an Exchange
Engineer at Microsoft:
"The problem in your case was 128 MB Multiplied by 250 users 31 GB
Approx.
But since the messages are sent to 250 users first it will create a
transaction logs for every transactions & then the database will have
only one copy per store. Now exchange stores single storage instance.
So in short all users for that particular store will access one copy."
So the entire attachement IS written to the log for each user. After
this, single isntance storage comes into play by making 1 copy per
database.
This would explain the large growth in the logs that I saw.
Thanks again for your replies.
.
- References:
- HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: sillz
- Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: Andy David {MVP}
- Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: sillz
- Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: Mark Arnold [MVP]
- Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: sillz
- Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- From: sillz
- HUGE Attachment Causes Transaction Logs to Fill Up Disk
- Prev by Date: RE: old 5.5 servers
- Next by Date: Re: Transporter Suite for Lotus Domino
- Previous by thread: Re: HUGE Attachment Causes Transaction Logs to Fill Up Disk
- Next by thread: Unable to send large emails NDR 5.2.3
- Index(es):
Relevant Pages
|
