Link to home
Start Free TrialLog in
Avatar of JohnDemerjian
JohnDemerjianFlag for United States of America

asked on

any downside to 100MB Transport Dumpster

EE

After reading about Exchange 2010 SP1 DAG, Transport Dumpster and AutoDatabaseMountDial I have decided I'd like to use a high transport dumpster setting of between 60-100MB.  Is there any down side, performance or recoverability wise to increasing the default this much?  Our message size limit is 30MB and I realize the recommendation is 1.5 x that size, but for added insurance during an automatic failover, I want the larger size.  Is there a down side?
Avatar of Jessie Gill, CISSP
Jessie Gill, CISSP
Flag of Canada image

I don't believe there is any real downside to doing what you are doing, but the transport dumpster has changed a bit in 2010, it no longer holds messages in the dumpster waiting for the size limit to be reached to truncate the dumpster.  The Dumpster in 2010 now receives feedback from the replication pipeline to determine which messages have been delivered and replicated.  Once the message has been committed to all copies it auto truncates the message.

http://technet.microsoft.com/en-us/library/dd638137(EXCHG.140).aspx
Avatar of JohnDemerjian

ASKER

can you describe precisely under what circumstances a message is at risk for being lost?  and does being lost mean no NDR to the sender?
ASKER CERTIFIED SOLUTION
Avatar of Jessie Gill, CISSP
Jessie Gill, CISSP
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Let's say that between the time a db goes offline on one server and online on another, the elapsed time is 10 seconds.  During that time I receive 50 megs of email destined for mailboxes on that db.  Where does that 50 meg sit while it waits for the db to come online?  Does it sit in a delivery queue?  Because I can't find info that explains how long mail will sit in queue.  All I can find is info about the shadow retry feature that tries a different hub transport, which I understand. But if the mailbox is offline trying a different path to it is pointless.

So what does the 50 meg of mail do for 10 seconds?

Thanks for working this through with me...
Avatar of Albert Widjaja
ok, if my Exchange Server 2010 not using DAG in the two mailbox servers, how much is the size for the ttransport dumpster size to allow me send and receive email with 50 MB attachment ?

[PS] C:\>Get-TransportConfig | fl *Max*
MaxDumpsterSizePerDatabase      : 50 MB (52,428,800 bytes)
MaxDumpsterTime                 : 7.00:00:00
MaxReceiveSize                  : 50 MB (52,428,800 bytes)
MaxRecipientEnvelopeLimit       : 5000
MaxSendSize                     : 50 MB (52,428,800 bytes)
ExternalDsnMaxMessageAttachSize : 25 MB (26,214,400 bytes)
InternalDsnMaxMessageAttachSize : 25 MB (26,214,400 bytes)

Open in new window