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

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

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

To resolve this issue, install the following update rollup:

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

For more information about the standby continuous replication, visit the following Microsoft website: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: