Clustered Mailbox Server: %2Physical Server: %3The cluster experienced a handoff or a failover. The database in storage group %1 was forced to mount after waiting %6 seconds.The known number of logs lost was: * The log file generated before the failure was: %4* The last log file successfully replicated to the passive node was: %5.

Details
Product: Exchange
Event ID: 2093
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: AutoMountReportMountAfter
Message: Clustered Mailbox Server: %2Physical Server: %3The cluster experienced a handoff or a failover. The database in storage group %1 was forced to mount after waiting %6 seconds.The known number of logs lost was: * The log file generated before the failure was: %4* The last log file successfully replicated to the passive node was: %5.
   
Explanation

The Warning event indicates that either a failover occurred or an administrator performed a Move-ClusteredMailboxServer task in the cluster continuous replication (CCR) environment. The Microsoft Exchange Replication Service setting, ForceDatabaseMountAfter, on the Mailbox server will force the database to mount regardless of whether all logs are copied in order to make the database available. This setting is based on time. If the setting is two hours and the replication service has been unable to copy all required logs after the failover, the database will be mounted at the end of two hours.

For more information about how to tune failover and mount settings in CCR, see How to Tune Failover and Mount Settings for Cluster Continuous Replication.

The Move-ClusteredMailboxServer cmdlet is used to initiate a scheduled outage of a clustered mailbox server between nodes. This situation contrasts with an unscheduled outage when the Mailbox server’s host fails. When the event occurs, the failover to the passive node occurs with some data loss because not all log files are copied from the failed active node. The event provides a detailed report on the data loss.

For more information about the Move-ClusteredMailboxServer cmdlet, see Move-ClusteredMailboxServer.

   
User Action

To resolve this warning, reseed the passive node. For more information, see How to Seed a Cluster Continuous Replication Copy.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply