We are getting lot of replication issues on both our DCs, I've done research but it basically just repeats what the event log says, which is not very helpful. What would cause this?
Replication does seem to work ok, since i created a test user and it ended up on the other DC, I deleted it, it was then deleted on the other DC.
These are the errors we are getting:
There seems to be a pattern, easier to post a pic then to try to explain:
It always starts at 3:12:56pm. Anyone ever seen this before? Oh and on the BDC it actually does the same, but at 6:01:06. And yes, I say BDC even though it's a 2003 environment. It's been migrated from NT4 long time ago so it still acts as PCD / BDC. Not sure why. If the primary DC goes down, everything goes down. The primary is the FSMO.
Replication does seem to work ok, since i created a test user and it ended up on the other DC, I deleted it, it was then deleted on the other DC.
These are the errors we are getting:
Code:
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 2/15/2010
Time: 3:12:56 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: TDHDC1
Description:
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=DomainDnsZones,DC=DOMAIN,DC=LOCAL
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: NTDS Replication
Event Category: Backup
Event ID: 2089
Date: 2/15/2010
Time: 3:12:56 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: TDHDC1
Description:
This directory partition has not been backed up since at least the following number of days.
Directory partition:
DC=ForestDnsZones,DC=DOMAIN,DC=LOCAL
'Backup latency interval' (days):
90
It is recommended that you take a backup as often as possible to recover from accidental loss of data. However if you haven't taken a backup since at least the 'backup latency interval' number of days, this message will be logged every day until a backup is taken. You can take a backup of any replica that holds this partition.
By default the 'Backup latency interval' is set to half the 'Tombstone Lifetime Interval'. If you want to change the default 'Backup latency interval', you could do so by adding the following registry key.
'Backup latency interval' (days) registry key:
System\CurrentControlSet\Services\NTDS\Parameters\Backup Latency Threshold (days)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.There seems to be a pattern, easier to post a pic then to try to explain:
It always starts at 3:12:56pm. Anyone ever seen this before? Oh and on the BDC it actually does the same, but at 6:01:06. And yes, I say BDC even though it's a 2003 environment. It's been migrated from NT4 long time ago so it still acts as PCD / BDC. Not sure why. If the primary DC goes down, everything goes down. The primary is the FSMO.
Last edited:
Facebook
Twitter