Select the product you need help with

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

Article ID: 2653334 - View products that this article applies to.

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.

Back to the top | Give Feedback

CAUSE

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

Back to the top | Give Feedback

RESOLUTION

To resolve this issue, install the following update rollup:

2608656

(http://support.microsoft.com/kb/2608656/ )

Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

Back to the top | Give Feedback

STATUS

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

Back to the top | Give Feedback

MORE INFORMATION

For more information about standby continuous replication, visit the following Microsoft website:

General information about standby continuous replication

(http://technet.microsoft.com/en-us/library/bb676502(EXCHG.80).aspx)

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

(http://technet.microsoft.com/en-us/library/bb331968(EXCHG.80).aspx)

Back to the top | Give Feedback