Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1
Topic Last Modified: 2007-08-20

This topic explains how to use the Exchange Management Console or the Exchange Management Shell to configure the transport dumpster feature on a Hub Transport server. The transport dumpster is an optional feature for cluster continuous replication (CCR) and local continuous replication (LCR), and it is enabled by default. The configuration settings for the transport dumpster are applied at the storage group level.

In this procedure, you change the default configuration settings for the transport dumpster. We recommend that you configure the MaxDumpsterSizePerStorageGroup parameter, which specifies the maximum size of the transport dumpster queue for each storage group, to a size that is 1.5 times the size of the maximum message that can be sent. For example, if the maximum size for messages is 10 megabytes (MB), you should configure the MaxDumpsterSizePerStorageGroup parameter with a value of 15 MB.

We also recommend configuring the MaxDumpsterTime parameter, which specifies how long an e-mail message should remain in the transport dumpster queue, to a value of 07.00:00:00, which is seven days. This amount of time is sufficient to allow for an extended outage to occur without loss of e-mail. When using the transport dumpster feature, additional disk space is needed on the Hub Transport server to host the transport dumpster queues. The amount of storage space required is roughly equal to the value of MaxDumpsterSizePerStorageGroup multiplied by the number of storage groups.

If you do not configure the Transport Dumpster, the default values will be used. The default value for the MaxDumpsterSizePerStorageGroup parameter is 18 MB, and the default value for the MaxDumpsterTime parameter is seven days. If either the size limit or time limit is reached, messages will be removed from the transport dumpster queue by order of first in, first out.

Note:
Setting either value to zero disables the transport dumpster for all CCR and LCR-enabled storage groups in the Exchange organization.

Before You Begin

Check the following before performing the procedure:

  • Make sure that you have enough space on each Exchange Hub Transport server to accommodate the data in the transport dumpster queue for each storage group.

  • Make sure that the account you use is delegated the Exchange Organization Administrator role. For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

Procedure

To use the Exchange Management Console to view and configure the transport dumpster settings

  1. Open the Exchange Management Console.

  2. Expand Organization Configuration, and then select Hub Transport.

  3. In the Results pane, select the Global Settings tab.

  4. Double-click Transport Settings.

  5. In the Transport Dumpster area, enter the appropriate values for the Maximum size per storage group (MB) and Maximum retention time (days) fields.

  6. Click OK to save the changes.

To use the Exchange Management Shell to determine the current settings of the transport dumpster

  • Run the following command to view the current settings for the transport dumpster:

    Copy Code 
    Get-TransportConfig
    Note:
    You should see a listing of the transport dumpster settings for the entire Exchange organization.

To use the Exchange Management Shell to configure the transport dumpster

  • Run the following command:

    Copy Code 
    Set-TransportConfig -MaxDumpsterSizePerStorageGroup <size> -MaxDumpsterTime <timespan>

    For example, to configure the maximum size of the dumpster per storage group to 30 MB with a dumpster life of seven days, run the following command:

    Copy Code 
    Set-TransportConfig -MaxDumpsterSizePerStorageGroup 30MB -MaxDumpsterTime 07.00:00:00

For More Information

For detailed syntax and parameter information about the cmdlet, see Set-TransportConfig.

For more information about managing LCR, see Managing Local Continuous Replication.