Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 832
Reply with quote  #1 

My latest one in the long line of odd, confused and broken AD's that I find.....WTF is this

I'm working on removing a lot of Domains out of a larger root domain. suffice to say there are interesting issues.

Today, I saw another new one, two DC's on the one LAN that are replicating OK.
If I force replication they appear only a few seconds behind each other.

But in repadmin /replsum, they appear with one DC >60 days..
This extract was taken with DC-On-The-Same-LANDC02 as the server the command was run on

Extract of the Source
DC-On-The-Same-LANDC01 >60 days 0 / 28 0
DC-On-The-Same-LANDC02 01h:38m:38s 0 / 54 0

Extract of the Destination
DC-On-The-Same-LANDC01 01h:40m:41s 0 / 54 0
DC-On-The-Same-LANDC02 >60 days 0 / 28 0

Whats with the >60 days for two DC's beside each other

Top of repadmin /relsum (quite a few more missing)

Code:

Beginning data collection for replication summary, this may take awhile:
..................................................
.....................

Source DSA largest delta fails/total %% error
CAw-DC05 :51s 0 / 26 0
DC-On-The-Same-LANDC01 >60 days 0 / 28 0
DC-On-The-Same-LANDC02 01h:38m:38s 0 / 54 0
Bad-guys-DC01 01h:51m:11s 0 / 82 0
Bad-guys-DC03 >60 days 26 / 134 19 (1256) The remote system is not available. For information about network troubleshooting, see Windows Help.
Bad-guys-DC04 01h:51m:11s 0 / 82 0

.
.
.
.

Bottom of the repadmin /replsum

Destination DSA largest delta fails/total %% error
DC-On-The-Same-LANDC01 01h:40m:41s 0 / 54 0
DC-On-The-Same-LANDC02 >60 days 0 / 28 0
Bad-guys-DC01 01h:38m:38s 0 / 82 0
Bad-guys-DC03 46m:56s 0 / 264 0
Bad-guys-DC04 01h:42m:42s 0 / 368 0
LA-DC01 18m:58s 0 / 82 0
Bad-guys-linked-DC01 01h:52m:12s 0 / 82 0
Bad-guys-linked-DC02 01h:45m:27s 0 / 82 0
Not-the-bad-guys-DC02 01h:48m:37s 0 / 108 0
Not-the-bad-guys-DC03 >60 days 26 / 134 19 (1256) The remote system is
not available. For information about network troubleshooting, see Windows Help.

 


 


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 199
Reply with quote  #2 
DCs have multiple partitions. What you are seeing is the slowest replication of any partition on the DC, which does not need to be the domain. On each machine, execute repadmin /showrepl. See what is going on.

Also, inspect the directory services eventlog.

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 832
Reply with quote  #3 
Just so I finish out the post.

This was in another AD report.
Bit log....but yes, other partitions had not replicated

Code:

Starting test: Replications
         REPLICATION LATENCY WARNING
         NotBadGuy4usDC01: This replication path was preempted by higher priority work.
            from NotBadGuy4usDC02 to NotBadGuy4usDC01
            Reason:
            Synchronization attempt failed because the destination DC is currently waiting to synchronize new 
partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. 
The destination partial attribute set is not a subset of source partial attribute set.
            The last success occurred at 2016-11-18 09:58:48.
            Replication of new changes along this path will be delayed.
         REPLICATION LATENCY WARNING
         NotBadGuy4usDC01: This replication path was preempted by higher priority work.
            from BadGuyDC03 to NotBadGuy4usDC01
            Reason:
            Synchronization attempt failed because the destination DC is currently waiting to synchronize new 
partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. 
The destination partial attribute set is not a subset of source partial attribute set.
            The last success occurred at 2016-11-18 10:43:49.
            Replication of new changes along this path will be delayed.
         REPLICATION-RECEIVED LATENCY WARNING
         NotBadGuy4usDC01:  Current time is 2016-11-18 11:18:50.
            DC=ForestDnsZones,DC=BadGuyroot,DC=IntLocal
               Last replication received from NotBadGuy1DC02OLD at 2016-04-25 15:04:39 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC03 at 2015-11-23 22:26:27 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy2DC03 at 2015-11-23 17:25:19 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy4DC03 at 2015-08-28 14:07:14 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy1DC01OLD at 2016-04-25 15:04:39 
               WARNING:  This latency is over the Tombstone Lifetime of 180days!
               Last replication received from NotBadGuy3DC05 at 2015-11-23 22:25:31 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            CN=Schema,CN=Configuration,DC=BadGuyroot,DC=IntLocal
               Last replication received from NotBadGuy1DC02OLD at 2016-04-25 15:04:39 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC03 at 2015-11-23 22:26:27 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy2DC03 at 2015-11-23 17:25:04 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy4DC03 at 2015-08-28 13:52:12 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy1DC01OLD at 2016-04-25 15:04:39 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC05 at 2015-11-23 22:10:31 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            CN=Configuration,DC=BadGuyroot,DC=IntLocal
               Last replication received from NotBadGuy1DC02OLD at 2016-04-25 15:04:12 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC03 at 015-11-23 22:26:22 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy2DC03 at 2015-11-23 17:25:04 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy4DC03 at 2015-08-28 14:07:08 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy1DC01OLD at 2016-04-25 15:04:14 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC05 at 2015-11-23 22:25:28 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            DC=NotBadGuy1coco,DC=IntLocal
               Last replication received from NotBadGuy1DC02OLD at 2016-04-25 15:05:43 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy1DC01OLD at 2016-04-25 15:05:07 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            DC=sligococo,DC=IntLocal
               Last replication received from NotBadGuy2DC03 at 2015-11-23 17:25:06 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            DC=kilkennycoco,DC=IntLocal
               Last replication received from NotBadGuy4DC03 at 2015-08-28 14:09:14 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
            DC=pilot,DC=IntLocal
               Last replication received from NotBadGuy3DC03 at 2015-11-23 22:26:45 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!
               Last replication received from NotBadGuy3DC05 at 2015-11-23 22:26:05 
               WARNING:  This latency is over the Tombstone Lifetime of 180 days!

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 199
Reply with quote  #4 
Man, what a mess. Looks like a combination of problems with the network and corrupt GCs. These guys -- with all due respect -- have no clue about AD.
__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.