I have 2 dc windows 2003: one is the master and it is called dc, the other is called fs and it is not synchronized with the master. On the fs server I stopped the service netlogon because I have had problems with the user's logon. The ad db is too old. On fs there are some events with the following ID: 13508 (replica file), 4000 (dns), [2089 (ntds replication, not enough reputation to post the link)
EVENT 2089 This directory partition has not been backed up since at least the following number of days. Directory partition:
CN=Schema,CN=Configuration,DC=domain,DC=com "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).
Are there some cmd to force a resync from dc to fs ?
and what's the problem ? why the replica is stopped ?