We help IT Professionals succeed at work.

Windows 2003 server event id 2089 NTDS Replication error (server crashed and still in AD)

I seem to be getting the error below:

This all started when the server crashed, I ran ntdsutil and removed the crashed server, but there must be another setting somewhere where the old server is still in the AD.

Any idea on how to remove this server from AD?

This directory partition has not been backed up since at least the following number of days.
Directory partition:
'Backup latency interval' (days):
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)
Watch Question

Top Expert 2013

Where are you seeing the old server there?  That is just telling you the box has not been backed up (the schema NC)

ntdsutil/metadata cleanup is the right thing to do for a crashed box.  Did it hold any FSMO roles?


Sajid Shaik MSystem Admin



I used ntdsutil and deleted the crash server. But I can't seem to find the crashed server causing the backup issue. I looked in dns and ad sites and it isn't listed.

Any other idea's?
Sandesh DubeyTechnical Lead
Top Expert 2011

This event( 2089 NTDS Replication) is logged when a partition is not backed up during the backup latency interval. Only one event error message is logged each day for each partition that a domain controller hosts.

You only have to backup the system state with ntbackup. The message will disappear and remind you after 90 days.

Regarding the old server which was crashed and removed from the network you need ran metadata cleanup to remove the instances of old server from AD database and dns.Refer below link.

If the remove server was FSMO role holder server you need to seize the role on other DC.

Hope this helps.
As its a replication issue If you look on sites are services you might see the server still listed there or as a replication partner to another dc.

You can delete the legacy server here and ensure ntdsutil metadata cleanup no longer lists the dead dc.

Netdom query dc returns all the dcs the domain knows about

Netdom query fsmo return the role holders. Check to see no roles are assigned to the legacy dc

Explore More ContentExplore courses, solutions, and other research materials related to this topic.