Article ID: 2653334 - View products that this article applies to.
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.
This issue occurs because transaction logs are truncated when there is a race condition and when SCR is running in a backup context.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2608656/ )Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about standby continuous replication, visit the following Microsoft website:
General information about standby continuous replicationFor 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
Article ID: 2653334 - Last Review: February 10, 2012 - Revision: 3.0