The reseed process is unsuccessful on the SCR passive node when circular logging is enabled in an Exchange Server 2007 environment

Article translations Article translations
Article ID: 2653334 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Assume that you enable the circular logging feature in a Microsoft Exchange Server 2007 environment, and then you reseed the standby continuous replication (SCR) on the passive node. In this situation, the reseed operation is unsuccessful, and the transaction log is truncated. Additionally, you have to manually copy the missing log file from another SCR node.

CAUSE

This issue occurs because transaction logs are truncated when there is a race condition and when SCR is running in a backup context. 

RESOLUTION

To resolve this issue, install the following update rollup:
2608656 Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about standby continuous replication, visit the following Microsoft website:
General information about standby continuous replication
For more information about how to enable or disable circular logging for a storage group by using the Exchange Management Console or the Exchange Management Shell, visit the following Microsoft website:
General information about how to enable or disable circular logging for a storage group

Properties

Article ID: 2653334 - Last Review: February 10, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft Exchange Server 2007 Service Pack 3, when used with:
    • Microsoft Exchange Server 2007 Standard Edition
    • Microsoft Exchange Server 2007 Enterprise Edition
Keywords: 
kbqfe kbfix kbexpertiseinter kbsurveynew KB2653334

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com