Export (0) Print
Expand All

How to Tune Failover and Mount Settings for Cluster Continuous Replication

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-10-30

This topic explains how to use the Exchange Management Shell to view and set the failover and mount attributes for a cluster continuous replication (CCR) environment. This topic also explains how to use the Exchange Management Console in Service Pack 1 (SP1) for Microsoft Exchange Server 2007 to tune the automatic database mount attribute.

  1. Open the Exchange Management Console.

  2. Expand Server Configuration, and then select Mailbox.

  3. In the result pane, right-click the clustered mailbox server (CMS) and select Properties.

  4. Select the Clustered Mailbox Server tab.

  5. Use the Auto database mount dial drop-down box to configure the desired failover availability settings.

    noteNote:
    This drop-down box only sets the value for AutoDatabaseMountDial. Use the Exchange Management Shell procedure later in this topic to set the ForcedDatabaseMountAfter parameter.
  6. Click OK to save the change.

  1. Open the Exchange Management Shell.

  2. Run the following command to obtain the current automatic database mount settings:

    Get-MailboxServer <CMSName> | format-list
    
  3. Run the following command to obtain the current transport dumpster settings:

    Get-TransportConfig | format-list
    

  1. Open the Exchange Management Shell.

  2. Run the following commands to set each automatic database mount attribute:

    Set-MailboxServer <CMSName> -AutoDatabaseMountDial:<Value>
    
    noteNote:
    <Value> must be set to Lossless, GoodAvailability, or BestAvailability.
    Set-MailboxServer <CMSName> -ForcedDatabaseMountAfter:<Value> 
    
    noteNote:
    <Value> must be set to a specified number or "unlimited."
    importantImportant:
    When the value for ForcedDatabaseMountAfter is reached, the database will be mounted regardless of whether the storage group copy is 1 log behind, 10 logs behind, or 1,000 logs behind, which could result in significant data loss. For this reason, this parameter should not be used if service level agreements (SLAs) guarantee a maximum on the amount of data loss that can be incurred.
To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft