|
View Full Version : Replication Issue?
I have a W2K AD forest with 2 domains: a main domain and a child domain.
There are 4 sites defined in AD. One site contains the main domain, one
site contains the child domain, and the other 2 sites have DCs for the main
domain. The site for the main domain contains 2 DCs.
I have not manually configured any replication links for the sites; when the
KCC creates the replication links, they appear to be incorrect. It
automatically created links between the 2 DCs at the main site and a link to
one of the remote sites. It also created a link between one of the remote
sites and the site with the child domain. Finally, it created a link
between the 2 remote sites.
Is this an appropriate configuration? Should I manually create links? I
realize the details may be scetchy. If more details are needed I can
provide them.
Thanks,
Jeff
|
Before you decide to manually create replication objects, please have a
check if the
topology is fully generated. You can do this by using DCDIAG(Support Tools
on CD):
DCDIAG /test:topology
If DCDIAG tells you that everything is OK(e.g. connected) - it's up to you
to decide
if you'd like to change the topology. But be carefull!
If you decide to change the replication topology take into account the
underlying network
topology(e.g. Hub and Spoke, etc).
--
Christian Schindler
MCSA / MCSE / MCT / CCEA
Senior Consultant
NTx BackOffice Consulting Group Austria
mailto:cns@ntx.at
"Jeff" wrote in message
news:urKph7f7DHA.2056@TK2MSFTNGP10.phx.gbl...
> I have a W2K AD forest with 2 domains: a main domain and a child domain.
> There are 4 sites defined in AD. One site contains the main domain, one
> site contains the child domain, and the other 2 sites have DCs for the
main
> domain. The site for the main domain contains 2 DCs.
>
> I have not manually configured any replication links for the sites; when
the
> KCC creates the replication links, they appear to be incorrect. It
> automatically created links between the 2 DCs at the main site and a link
to
> one of the remote sites. It also created a link between one of the remote
> sites and the site with the child domain. Finally, it created a link
> between the 2 remote sites.
>
> Is this an appropriate configuration? Should I manually create links? I
> realize the details may be scetchy. If more details are needed I can
> provide them.
>
> Thanks,
>
> Jeff
>
>
|
I will run the test with dcdiag-that is a good idea. One follow up
question:
Why would the KCC create a topology where one remote site replicates to
another remote site? Logically, it seems like all remote sites should
replicate back to the DCs at our main site?
Perhaps my logic is not right?
Thanks,
JEff
|
The KCC creates the topology based on the site links.
Site links are per default "transitive" which means that not only the main
site is able to replicate to the remote site, but also the remote sites are
able to
replicate to each other.
You can turn off transitivity in AD Sites & Services: Select "Intersite
Transports", open the
properties of the "IP" container and uncheck the checkbox "Bridge all site
links"
--
Christian Schindler
MCSA / MCSE / MCT / CCEA
Senior Consultant
NTx BackOffice Consulting Group Austria
mailto:cns@ntx.at
"Jeff" wrote in message
news:#wkKzAp7DHA.1052@TK2MSFTNGP12.phx.gbl...
> I will run the test with dcdiag-that is a good idea. One follow up
> question:
>
> Why would the KCC create a topology where one remote site replicates to
> another remote site? Logically, it seems like all remote sites should
> replicate back to the DCs at our main site?
>
> Perhaps my logic is not right?
>
> Thanks,
>
> JEff
>
>
|
If I turn of transitivity, will the KCC re-create the replication links?
Thanks for your assistance on this,
Jeff
"Christian Schindler" wrote in message
news:uTI%23g2u7DHA.1632@TK2MSFTNGP12.phx.gbl...
> The KCC creates the topology based on the site links.
>
> Site links are per default "transitive" which means that not only the main
> site is able to replicate to the remote site, but also the remote sites
are
> able to
> replicate to each other.
>
> You can turn off transitivity in AD Sites & Services: Select "Intersite
> Transports", open the
> properties of the "IP" container and uncheck the checkbox "Bridge all site
> links"
>
> --
> Christian Schindler
> MCSA / MCSE / MCT / CCEA
>
> Senior Consultant
>
> NTx BackOffice Consulting Group Austria
> mailto:cns@ntx.at
>
> "Jeff" wrote in message
> news:#wkKzAp7DHA.1052@TK2MSFTNGP12.phx.gbl...
> > I will run the test with dcdiag-that is a good idea. One follow up
> > question:
> >
> > Why would the KCC create a topology where one remote site replicates to
> > another remote site? Logically, it seems like all remote sites should
> > replicate back to the DCs at our main site?
> >
> > Perhaps my logic is not right?
> >
> > Thanks,
> >
> > JEff
> >
> >
>
>
|
Yes it will, but it takes some time.
--
Christian Schindler
MCSA / MCSE / MCT / CCEA
Senior Consultant
NTx BackOffice Consulting Group Austria
mailto:cns@ntx.at
"Jeff" wrote in message
news:eKsVMCx7DHA.2644@TK2MSFTNGP11.phx.gbl...
> If I turn of transitivity, will the KCC re-create the replication links?
>
> Thanks for your assistance on this,
>
> Jeff
>
> "Christian Schindler" wrote in message
> news:uTI%23g2u7DHA.1632@TK2MSFTNGP12.phx.gbl...
> > The KCC creates the topology based on the site links.
> >
> > Site links are per default "transitive" which means that not only the
main
> > site is able to replicate to the remote site, but also the remote sites
> are
> > able to
> > replicate to each other.
> >
> > You can turn off transitivity in AD Sites & Services: Select "Intersite
> > Transports", open the
> > properties of the "IP" container and uncheck the checkbox "Bridge all
site
> > links"
> >
> > --
> > Christian Schindler
> > MCSA / MCSE / MCT / CCEA
> >
> > Senior Consultant
> >
> > NTx BackOffice Consulting Group Austria
> > mailto:cns@ntx.at
> >
> > "Jeff" wrote in message
> > news:#wkKzAp7DHA.1052@TK2MSFTNGP12.phx.gbl...
> > > I will run the test with dcdiag-that is a good idea. One follow up
> > > question:
> > >
> > > Why would the KCC create a topology where one remote site replicates
to
> > > another remote site? Logically, it seems like all remote sites should
> > > replicate back to the DCs at our main site?
> > >
> > > Perhaps my logic is not right?
> > >
> > > Thanks,
> > >
> > > JEff
> > >
> > >
> >
> >
>
>
|
Christian,
One followup question: When I look at the properties for the automatically
generated replication links, there is a spot where I can change what server
the site replicates from. Is changing that the same as creating a link
manually? Should I avoid changing that property of the replication link?
Thanks,
Jeff
"Christian Schindler" wrote in message
news:uTI%23g2u7DHA.1632@TK2MSFTNGP12.phx.gbl...
> The KCC creates the topology based on the site links.
>
> Site links are per default "transitive" which means that not only the main
> site is able to replicate to the remote site, but also the remote sites
are
> able to
> replicate to each other.
>
> You can turn off transitivity in AD Sites & Services: Select "Intersite
> Transports", open the
> properties of the "IP" container and uncheck the checkbox "Bridge all site
> links"
>
> --
> Christian Schindler
> MCSA / MCSE / MCT / CCEA
>
> Senior Consultant
>
> NTx BackOffice Consulting Group Austria
> mailto:cns@ntx.at
>
> "Jeff" wrote in message
> news:#wkKzAp7DHA.1052@TK2MSFTNGP12.phx.gbl...
> > I will run the test with dcdiag-that is a good idea. One follow up
> > question:
> >
> > Why would the KCC create a topology where one remote site replicates to
> > another remote site? Logically, it seems like all remote sites should
> > replicate back to the DCs at our main site?
> >
> > Perhaps my logic is not right?
> >
> > Thanks,
> >
> > JEff
> >
> >
>
>
|
Yes that is ths same. If you consider creating the replication objects
yourself, just keep
in mind, that the KCC will not overrule your connections objects. In other
words:
If you're not creating all necessary connection objects, the topology will
not be
fully connected.
I prefer to let the KCC do the work for me.
--
Christian Schindler
MCSA / MCSE / MCT / CCEA
Senior Consultant
NTx BackOffice Consulting Group Austria
mailto:cns@ntx.at
"Jeff" wrote in message
news:uSIHm497DHA.2392@TK2MSFTNGP11.phx.gbl...
> Christian,
>
> One followup question: When I look at the properties for the automatically
> generated replication links, there is a spot where I can change what
server
> the site replicates from. Is changing that the same as creating a link
> manually? Should I avoid changing that property of the replication link?
>
> Thanks,
>
> Jeff
>
> "Christian Schindler" wrote in message
> news:uTI%23g2u7DHA.1632@TK2MSFTNGP12.phx.gbl...
> > The KCC creates the topology based on the site links.
> >
> > Site links are per default "transitive" which means that not only the
main
> > site is able to replicate to the remote site, but also the remote sites
> are
> > able to
> > replicate to each other.
> >
> > You can turn off transitivity in AD Sites & Services: Select "Intersite
> > Transports", open the
> > properties of the "IP" container and uncheck the checkbox "Bridge all
site
> > links"
> >
> > --
> > Christian Schindler
> > MCSA / MCSE / MCT / CCEA
> >
> > Senior Consultant
> >
> > NTx BackOffice Consulting Group Austria
> > mailto:cns@ntx.at
> >
> > "Jeff" wrote in message
> > news:#wkKzAp7DHA.1052@TK2MSFTNGP12.phx.gbl...
> > > I will run the test with dcdiag-that is a good idea. One follow up
> > > question:
> > >
> > > Why would the KCC create a topology where one remote site replicates
to
> > > another remote site? Logically, it seems like all remote sites should
> > > replicate back to the DCs at our main site?
> > >
> > > Perhaps my logic is not right?
> > >
> > > Thanks,
> > >
> > > JEff
> > >
> > >
> >
> >
>
>
|
|
|
|