Microsoft KB Archive/944934

= Event ID 524 and event ID 2099 are logged on the passive node when you seed a storage group copy in an Exchange 2007 CCR environment by using the Update-StorageGroupCopy cmdlet =

Article ID: 944934

Article Last Modified on 11/21/2007

-

APPLIES TO


 * Microsoft Exchange Server 2007 Enterprise Edition

-



SYMPTOMS
You can seed a storage group copy in a Microsoft Exchange Server 2007 cluster continuous replication (CCR) environment by using the Update-StorageGroupCopy cmdlet. In some cases, event ID 524 and event ID 2099 are logged on the passive node when replication is resumed after the seeding task has finished. These events indicate that data loss has occurred.

The following are the details of event ID 524 and of event ID 2099. Event Type: Warning

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 524

Description:

Microsoft.Exchange.Cluster.ReplayService (2396) Recovery E01: Database C:\Program Files\Microsoft\Exchange Server\Mailbox\ESE524\ESE524-MBX.edb has lost 6 committed log files (488-493), however lost log resilience has allowed ESE to recover this database to a consistent state, but with data loss. Recovery could only locate log files up to 487.

Note Event ID 524 is issued by the Extensible Storage Engine (ESE). Additionally, event ID 524 is logged in the context of the Microsoft.Exchange.Cluster.ReplayService (2396) service that is running on the passive node. Event Type: Information

Event Source: MSExchangeRepl

Event Category: Service

Event ID: 2099

Description:

The Microsoft Exchange Replication Service requested that Hub Transport server  resubmit messages between time periods   and.



CAUSE
The Update-StorageGroupCopy cmdlet seeds the storage group copy with a current copy of the active database. However, the cmdlet does not copy any log files. After replication is resumed, the Microsoft Exchange Replication service may replay a log file before all required log files are copied successfully from the active node to the passive node.



RESOLUTION
In the situation that is described in the &quot;Symptoms&quot; section, no data loss occurs. You can use the Get-StorageGroupCopyStatus cmdlet to verify that the storage group copy is healthy. Therefore, you can safely ignore these events. These events do not always appear. Replication is successfully resumed when all required log files are copied to the passive node.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about how to seed a storage group copy in a CCR environment, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/bb124706.aspx

Keywords: kbtshoot kbprb kbexpertiseinter KB944934

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.