Transport Dumpster feature is only specific to the Hub Transport server. Most important thing to remember is that transport dumpster does not recover all the data, but some data only. For example, an email sent to the Hub Transport at the time of disaster may not be included in the transport dumpster.
Transport
dumpster maintains a rolling queue of al email messages that are
recently been delivered to users whose mailboxes are hosted on that CCR
environment. During disaster and its recovery, transport dumpster redeliver those messages automatically.
Dumpster transport
feature is enabled by default and can be disabled if not required. But
If enabled, you must also take into account an increased disk I/O.
MaxDumpsterSizePerStorageGroup
is the amount of space allocated to the storage group for messages
within the dumpster. Microsoft recommends the value should be 1.5*the
maximum message size. For example, if the maximum message size is 20MB,
then dumpster value should ne 30MB. If no maximum message size is
configured, then average message size can be considered to calculate dumpster value.
MaxDumpsterTime defines
for how many days, hours, minutes and seconds a message will be stored
in the dumpster. The default value is 7.0.0.0 which means 7 days, 0
hours, 0 minutes, 0 seconds. Microsoft recommends keeping these default
values so no need to alter these values.
Get-transportconfig
Â
Below command will set the Maximum dumpster size to 30MB.
Set-TransportConfig –MaxDumpsterSizePerStorageGroup 30MB
Below command will set the maximum dumpster time from 7 days to 6 days (DD.HH:MM.SS).
Set-TransportConfig –MaxDumpsterTime 6.6:0:0
Above values can also be set from the EMC.
1. Expand the Organization Configuration.
2. Highlight the Hub Transport.
3. Select the Global Settings tab in the result pane and you will see the Transport Setting object.
4. Right click on Transport Settings and open its Properties..
Let us assume that message size is 20MB, which means that transport
dumpster parameter will be set to 30MB. Mike has sent 8 emails to John
which contains some attachment having 5MB in size each. Since dumpster
size is set to 30MN, so only 6 emails will be stored in the dumpster
before it reaches capacity.
|
Message#
|
From
|
To
|
Msg Size
|
|
1
|
Mike
|
John
|
5MB
|
|
2
|
Mike
|
John
|
5MB
|
|
3
|
Mike
|
John
|
5MB
|
|
4
|
Mike
|
John
|
5MB
|
|
5
|
Mike
|
John
|
5MB
|
|
6
|
Mike
|
John
|
5MB
|
When Mike will send the 7th email, then first message will be removed from the transport dumpster, since only 30MB can be stored in the transport dumpster. Therefore, transport dumpster will look like below:-
|
Message#
|
From
|
To
|
Msg Size
|
|
2
|
Mike
|
John
|
5MB
|
|
3
|
Mike
|
John
|
5MB
|
|
4
|
Mike
|
John
|
5MB
|
|
5
|
Mike
|
John
|
5MB
|
|
6
|
Mike
|
John
|
5MB
|
|
7
|
Mike
|
John
|
5MB
|
Similar
process will occur with the MaxDumpsterTime. Let us assume that
MaxDumpsterTime value has been set to 5 days, which means that when new
message will come, then old messages will be removed from the queue.
Like below:-
|
Message#
|
From
|
To
|
Date
|
Msg Size
|
|
1
|
Mike
|
John
|
10th Feb.2010
|
5MB
|
|
2
|
Mike
|
John
|
11th Feb.2010
|
5MB
|
|
3
|
Mike
|
John
|
12th Feb.2010
|
5MB
|
|
4
|
Mike
|
John
|
13th Feb.2010
|
5MB
|
|
5
|
Mike
|
John
|
14th Feb.2010
|
5MB
|
Since
MaxDumpsterTime parameter is set to 5 days, so only messages from last 5
days will be stored. When a new message will come on 15th Feb.2010, then old message of 10th Feb.2010 will be deleted as shown below:-
|
Message#
|
From
|
To
|
Date
|
Msg Size
|
|
2
|
Mike
|
John
|
11th Feb.2010
|
5MB
|
|
3
|
Mike
|
John
|
12th Feb.2010
|
5MB
|
|
4
|
Mike
|
John
|
13th Feb.2010
|
5MB
|
|
5
|
Mike
|
John
|
14th Feb.2010
|
5MB
|
|
6
|
Mike
|
John
|
15th Feb.2010
|
5MB
|
