Re: Sites and Services config. with 12 Sites
- From: "Harj" <cisqokid@xxxxxxxxx>
- Date: 7 Jul 2006 09:22:30 -0700
Hi,
You need a site link between the sites that will be replicating with
each other.
Site link bridge is created to build a transitive and logical link
between two sites that do not have an explicit site link. The site link
bridge is created only when the transitivity of the site link is
disabled, meaning if you have three sites. 1, 2, and 3. Site 1 has a
link to site 2, and there is another link between site 2 and site 3.
Here you notice there is no site link between site 1 and site 3. So if
site link transitivity is disabled, site 1 and 3 cannot communicate. A
site link bridge allows site 2 to act as a router for communication
between site 1 and site 3.
By default, all site links are transitive and it is recommended to keep
transitivity enabled by not changing the default value of Bridge all
site links (enabled by default). However, you will need to disable
Bridge all site links and complete a site link bridge design if:
Your IP network is not fully routed. When you disable Bridge all site
links, all site links are considered nontransitive, and you can create
and configure site link bridge objects to model the actual routing
behavior of your network.
-Or-
You need to control the replication flow of the changes made in Active
Directory. By disabling Bridge all site links for the site link IP
transport and configuring a site link bridge, the site link bridge
becomes the equivalent of a disjointed network. All site links within
the site link bridge can route transitively, but they do not route
outside of the site link bridge.
BRIDGEHEAD SERVER
By default, the Active Directory replication topology generator, the
Knowledge Consistency Checker (KCC), automatically chooses servers to
act as bridgehead servers. However, if you are an administrator, you
may select one or more domain controllers in the site to be preferred
bridgehead servers. These servers are used exclusively to replicate
changes collected from the site. Even though you may have
administratively configured several domain controllers as preferred
bridgehead servers, the KCC chooses one of these servers to become the
bridgehead server for the site. However, if you choose only one
bridgehead server for a particular site, and that server becomes
unavailable, the KCC does not choose another domain controller to be
the bridgehead server. Therefore, if you assign a preferred bridgehead
server, you should assign more than one.
I hope this helps
Harj Singh
Power Your Active Directory Investment
www.specopssoft.com
Zeno wrote:
I'm sortof new to this sites and service thing......
Our co. is in the process of designing an AD infrastructure... in the
design we will have a total of 3 countries and each country will have a
major site where there will be at least 2+ DCs and smaller regional
offices with 1 DC connected to the major site.
From what I've gathered so far reading all the things about sites andservices....
We plan to have set the major site in each country to replicate with
the major sites in the other countries, while the smaller regional
offices in each country will replicate with the major site in the
country.
Given this assumption, I'm going to use a star topology to connect the
three countries main sites an also star for the regional offices to the
countries main site.
Now what I;m not sure is how I define the Bridgehead server for the
main sites that have more than 1DC, how to define which DC will be the
one replicating with other sites.
When should I use a "Site Link" and when a "Site Link Bridge"
.
- Follow-Ups:
- Re: Sites and Services config. with 12 Sites
- From: Zeno
- Re: Sites and Services config. with 12 Sites
- References:
- Sites and Services config. with 12 Sites
- From: Zeno
- Sites and Services config. with 12 Sites
- Prev by Date: Re: ADAMSync Issues.
- Next by Date: Re: Group member of another group
- Previous by thread: Sites and Services config. with 12 Sites
- Next by thread: Re: Sites and Services config. with 12 Sites
- Index(es):
Relevant Pages
|
