Replication topology question

  • Thread starter Thread starter Neil Ruston
  • Start date Start date
N

Neil Ruston

Let's say I have 3 sites, all connected to each other at
the physical level (A-B, B-C, A-C).

I want to ensure that all these sites are connected to
each other with connection objects and not allow the KCC
to replicate from A-C via B, for example.

What is my best option here? Manual connection objects? A
site link with all 3 sites as members? The costs are all
the same, from site to site.

Thanks,
Neil
 
No need to do manual connection objects at all.
First, are you running 2000 or 2003? Just gives me some context.

Either way, the setting you'd be most interested in is bridge all site
links. Basically, let's say you define a link from A<->B and B<->C. With
bridge all site links enabled (default) the KCC would assume A can talk to
C. Without it enabled, it will not make that assumption.

I'd check out the 2000 branch office deployment guide for more information
about this. It goes into detail.
In 2003 we added some new stuff (a whole new KCC mode, not to mention KCC
scalability with large numbers of sites which I know doesn't help you with 3
sites, but just wanted to mention it :-) ) but from what you're describing
the 2000 KCC can do it with ISTG enabled without a problem.

~Eric
 
Thanks Eric.

We're using w2k and have ~ 100 sites. I used 3 as an
example only. :)

My question is this: if I define links A-B, B-C, A-C how
do I ensure that the KCC constructs connection objects
from A-B, B-C and A-C and not simply A-B and B-C (Assuming
all costs are the same)? Currently we use manual
connection objects to ensure that A and C also replicate
directly (and assign bridgehead roles in these sites too).

This has a large admin overhead and I wondered if adding
all 3 sites to one site link would result in KCC created
connection objects between all sites (much like a mesh
topology).

Any comments?

Neil
-----Original Message-----
No need to do manual connection objects at all.
First, are you running 2000 or 2003? Just gives me some context.

Either way, the setting you'd be most interested in is bridge all site
links. Basically, let's say you define a link from A<->B
Click to expand...
and B said:
bridge all site links enabled (default) the KCC would assume A can talk to
C. Without it enabled, it will not make that assumption.

I'd check out the 2000 branch office deployment guide for more information
about this. It goes into detail.
In 2003 we added some new stuff (a whole new KCC mode, not to mention KCC
scalability with large numbers of sites which I know doesn't help you with 3
sites, but just wanted to mention it :-) ) but from what you're describing
the 2000 KCC can do it with ISTG enabled without a problem.

~Eric

--
Eric Fleischman [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights


Neil Ruston said:
Let's say I have 3 sites, all connected to each other at
the physical level (A-B, B-C, A-C).

I want to ensure that all these sites are connected to
each other with connection objects and not allow the KCC
to replicate from A-C via B, for example.

What is my best option here? Manual connection objects? A
site link with all 3 sites as members? The costs are all
the same, from site to site.

Thanks,
Neil
Click to expand...


.
Click to expand...
 
Back
Top