Hello.
I have a question regarding repadmin command and the Outbound Neighbors for Change Notification. In the command "dc1" represents the DC I'm running repadmin against. If I run the following command
repadmin /showreps dc1 /repsto
I receive the following result
DC=foo,DC=local
site1\dc2 via RPC
DSA object GUID: aaaaaaa-aaaaa-aaaaa-aaaaa-aaaaaa
Address: aaaaaaa-aaaa-aaaaa-aaaaaa-aaaaaa._msdcs.foo.local
WRITEABLE
Last attempt @ 2015-02-19 10:37:58 was successful.
My confusion is around the Last attempt field. This connection object is for the domain partition and I know that changes are occurring on it constantly on the DC dc1, however the Last Attempt field shows a time from several hours ago. If
I go look at the Inbound connection on the partner DC (dc2) that is receiving the change notifications I can see that it is replicating from this DC (dc1) constantly. I know this because the Last Attempt field for the inbound connection on dc2
is never more than a few seconds old and the OU/PU fields are incrementing constantly.
DC1 and DC2 are in the same site, so replication between them is driven by change notification, not a schedule.
Shouldn't the Last Attempt field on the Outbound Neighbors for Change Notification be the same or very close to the Last Attempt field on the Inbound Neighbors on the partner DC?
I can understand why the Last Attempt field on Outbound Neighbors for Change Notification would be extremely old if the partition was the config or schema partition. Changes occur on those partitions extremely rarely, and the only replication that
occurs would be the schedule intersite or intrasite replication, which isn't driven by change notification
Any insight would be appreciated.