Link to home
Create AccountLog in
Avatar of john_991
john_991

asked on

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:
CN=Schema,CN=Configuration,DC=abc,DC=com
 
'Backup latency interval' (days):
30
 
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)
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

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?

Thanks

Mike
Avatar of john_991
john_991

ASKER

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?
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.
http://sandeshdubey.wordpress.com/2011/10/12/metadata-cleanup-of-a-domain-controller/
http://www.petri.co.il/delete_failed_dcs_from_ad.htm

If the remove server was FSMO role holder server you need to seize the role on other DC.
http://sandeshdubey.wordpress.com/2011/10/07/how-to-transfer-or-seize-fsmo-roles/

Hope this helps.
ASKER CERTIFIED SOLUTION
Avatar of Radweld
Radweld
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer