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.
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: