Re: Replication Topology

Hi
Additional info
http://technet2.microsoft.com/windowsserver/en/library/c238f32b-4400-4a0c-b4fb-7b0febecfc731033.mspx?mfr=true


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10AB32A9-E46C-4D91-874E-6209E267EF51@xxxxxxxxxxxxxxxx
We recently moved away from the single-site model, moved our DC's into
appropriate sites, assigned subnets as appropriate. We have about 7 sites
now in AD including our main site, all with DC's. The remaining sites
subnets that do not have a DC on-site are assigned to the main site (which
has 4 DC's). We migrated about 2 sites per day over a week so we could
look
at bandwidth, etc.

Everything is working well, we have decreased bandwidth and sped up logon
processing, share access, etc. for the remote sites that have a DC. No
replication errors.

However, now that it has settled for a few days, the KCC has created a
less-than-desirable replication topology. Essentially, the 4 DC's in our
main site now all partner to each other. Only 1 DC at the main site has a
single link to any of the remote sites, call it Site 2. Then Site 2 DC
has a
link to the 1 DC of our Main Site, and links to each of the other DC's in
each Site. However, the other 5 sites, each with 1 DC, now only have 1
replication partner which is the Site 2 DC.

This does not seem right, as what I read says the KCC should balance out
so
that every DC has at least 2 replication partners. All sites use the
DEFAULTIPSITELINK transport. All of these sites are connected via a T1
MPLS
link, the main site having a 4-T1 bonded link.

I have chosen one of the other Sites and done the Check Replication
Topology
action in the Sites & Services container, but it did nothing to create new
(or more) links.

Any thoughts/ideas? I would like the KCC to manage this rather than
creating manual partners, but I don't understand why it is behaving this
way.

Thanks!




.

Relevant Pages

  • Re: Operations Masters
    ... The File Replication Service SYSVOL ready test ... MCSE, MVP Directory Services ... DC1, it does not connect to DC1, instead it connect to DC2. ... all to the same DNS server without secondaries. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Do Child DCs need unrestricted IP access to Root DCs?
    ... MVP Directory Services ... "Jorge Silva" wrote in message ... Check Microsoft's documentation about Active Directory Replication over Firewalls, ... Do all child DC's need unrestricted IP access to all root DC's for AD replication to work successfully? ...
    (microsoft.public.windows.server.active_directory)
  • Re: [WARNING] Failed to query SPN registration on DC
    ... MCSE, MVP Directory Services ... "Andrew Story" wrote in message ... Service records exist in the newly promoted DC for itself, but not on it's replication partner. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Changing IP address on Domain Controllers
    ... Redefine the ACSS subnets and sites. ... Re-Register the DC new address. ... Run replication and make sure that can replicate with its partners. ... MCSE, MVP Directory Services ...
    (microsoft.public.windows.server.active_directory)
  • Re: [WARNING] Failed to query SPN registration on DC
    ... I;ve read those troubleshooting tips yes. ... There's alot to go at in there ... MCSE, MVP Directory Services ... replication cannot occur due to a DNS lookup failue. ...
    (microsoft.public.windows.server.active_directory)