Clustered Mailbox Server: %2Physical Server: %3Storage group %1 contains a public folder database that will not be automatically mounted because there was data loss. *The last log generated before the Move-ClusteredMailboxServer operation or failover was: %4* The last log successfully replicated to the passive node was: %5Attempts to copy to the last logs from the active node were not successful. Error code: %6.

Details
Product: Exchange
Event ID: 2094
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: AutoMountReportPublicFolderMountNotAllowed
Message: Clustered Mailbox Server: %2Physical Server: %3Storage group %1 contains a public folder database that will not be automatically mounted because there was data loss. *The last log generated before the Move-ClusteredMailboxServer operation or failover was: %4* The last log successfully replicated to the passive node was: %5Attempts to copy to the last logs from the active node were not successful. Error code: %6.
   
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 current active node that contains the public folder database was not mounted because some log files could not be copied over from the failed active node. The failover settings for a Mailbox server such as the ForceDatabaseMountAfter or the AutoDatabaseMountDial attributes do not apply to a public folder database. A public folder database will not mount if there is a lossy failover. The event provides details on the missing log files.

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.

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

   
User Action

To resolve the warning, do one or more of the following:

  • View the detailed event description and see whether you can manually copy the log files from the failed node. Then perform a reseed on the passive node. For more information, see How to Seed a Cluster Continuous Replication Copy.

  • Wait for the passive node to come back online which will make the missing log files available.

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