RE: [ActiveDir] Loose vs strict replication consistency

[Sakari Kouti]

Title: Loose vs strict replication consistency

Hi Neil,

 

> W2K DC all SPs: loose

Yes.

 

> W2K DC upgraded to W2k3: loose

Yes.

 

> w2k3 DC fresh built into new forest: strict

Yes.

 

> w2k3 DC fresh built into existing forest: loose

Not sure.

If someone reading this list has such a DC (the last case I'm not sure of), he or she could check the registry value "Strict Replication Consistency" in HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NTDS, Parameters to see if it is 1 (strict) or 0 (loose).

 

NB. Independent of lingering object detection�and independent of the strict/loose consistency setting�Windows Server 2003 always quarantines a source domain controller�s partition (i.e., source replica) if replication has not succeeded for more than a tombstone lifetime (default 60 days).

 

If you consequently use the Replicate Now operation of the Sites and Services snap-in, you will get the error �cannot replicate because the time since the last replication has exceeded the tombstone lifetime.� You would also probably get an error with the event ID 2042 in your event log. To recover from this error, first delete any lingering objects with repadmin /removelingeringobjects. Next, if DC2 did quarantine DC1, force the replication with a command such as the following:

repadmin /repl DC2 DC1 DC=sanao,DC=com /force

This fixes the problem for one partition, but when you try Replicate Now again, you may get the same error, but this time referring to the
next partition. At worst, you must issue the command also for the configuration and schema partitions, ForestDnsZones and DomainDnsZones, for any other application partitions, and in the case of a global catalog server, for each other domain in the forest.

 

There is also a registry setting to turn this check off, but it's safer to use the repadmin command, so that the next time this would happen, the protection would still be on.

 

Yours, Sakari

 

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruston, Neil
Sent: Friday, January 21, 2005 12:53 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Loose vs strict replication consistency

OK, so I understand what loose and strict repl. consistency *mean* and how a DC behaves in both scenarios, but am unsure which default behaviour is adopted by various OS and SP levels.

Is the following summary correct?

- W2K DC all SPs: loose
- W2K DC upgraded to W2k3: loose
- w2k3 DC fresh built into existing forest: loose
- w2k3 DC fresh built into new forest: strict

I assume therefore, that if I demote/rebuild as w2k3/promote my w2k DCs in my forest, then they will adopt "loose" as the default behaviour. Lingering objects may occur and can be removed as and when detected.

I referenced http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url="">

Thanks,
neil

==============================================================================
This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================