Site link bridges always needed?

[Guest]

Hello,

i'm now working on the replication setting of our company.
We have 1 forest/domain with several branch offices.
For each office we have a site configured.

I show you a example how i would like to configure the ad sites mmc:

Sub_Site1 Sub_Site2
| |
MAIN_Site
| |
Sub_Site3 Sub_Site4

I have deactivated the "Establish site link bridges between all sites"
checkbox,
because i want to have minimum replication traffic on all of the branch
offices.

So my question is now:
Do i need this site link bridges always? Because i want only that the DC
from the Sub_Sites replicates to my DC in my Main_Site.
Or is it important, that the Sub_Site DC's can replicate to each other?

There are no special applications or services used at the branch offices.
Am i right, that if i configure ad sites like shown above is the best way
for minimum replication traffic?

Thank you for help.
Best regards,
Karl-Heinz Fuchs

 

[Mark Renoden [MSFT]]

Hi

Site link bridging means that if there is IP connectivity between the branch
sites and all DCs in the main site are unavailable, connection objects for
replication may be built to overcome the outage and to ensure that the
branch sites remain in sync. Provided the hub site DCs remain online, the
ISTG will only build connection objects for replication that follow the site
link topology.

Turning off site link bridging means that the ISTG will only allow
connection objects that follow the site link topology even when there is a
hub site outage. It means less redundancy but less administrative
monitoring after a hub site outage to restore desirable replication paths.

I doubt it has an impact on overall replication traffic. It just means that
the traffic may take a different path to the one you intended.

--
Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jorge de Almeida Pinto [MVP - DS]]

disabling that might impact your DFS deployment if you have one...

also see:
http://blogs.msdn.com/spatdsg/archive/2006/10/16/dfs-and-bridge-all-site-links.aspx