Impact of Active Directory replication lag on Business Continuance

If the Active Directory replication lag is more than the threshold value, the re-creation of the Exchange instance can fail at the Business Continuance site.

The system gives an error message:

 Event Type:Error Event Source:MSExchangeSetup Event Category:Microsoft Exchange Setup Event ID:1002 Date:2/15/2008 Time:10:22:56 AM User:N/A Computer:VM24C Description: Exchange Server component Clustered Mailbox Server failed. Error: Error: The computer account 'vm24aSCC' was created on the domain controller, but has not replicated to the desired domain controller (EXCH7.extest.lab.netapp.com) after waiting approximately 60 seconds. Please wait for the account to replicate and re-run setup /newcms.

When SnapManager encounters this error, it makes three attempts to recover the Exchange instance; the interval between attempts is 180 seconds. To prevent such errors, ensure the following:

The intra-site and inter-site replication lags are minimum and within the threshold.
All Active Directory replication links work properly with minimal lag.

For more information about minimizing the intra-site and inter-site replication lags, see Microsoft documentation.