General discussion


replication inter-sites, rep. partner

I manage a network with 16 offices total. Each office has only one DC except the HQ that has 2 Checking the connection in sites and services i found out that most of the DC (10) have the same 3 replication partners, 1 site have only one partner and those 3 DC have connections with almost any DC of those 16 sites.
By replication partner i mean connection objects in the NTDS site object.
My question is, is it normal that almost every DC is partner with those 3? what does it means? The DC that only have one connection or replication partner, is it going to be in "worst shape"? When changes happen should i expect more traffic with those 3 DC? is this configuration fine in general? You can see a graphic in


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Whatme? In reply to replication inter-sites, ...

Well your web site didn't work but... You don't have to replicate with all the sites. It depends on your setup. If you have a main site or top level forest you may want everything to replicate with that site so every site should have that as their replication partner. Example. I company w/ 10 sites. Boston is home base. Everything may need to replicate with home base so ensure you have appropriate reps. If New York has a database you may have to ensure taht everything replicates to that as well. All this assumes that Boston holds some or all of the FMSO roles. You can always add a replication partner if you need to

Collapse -

by REZUMA In reply to

Poster rated this answer.

Collapse -

by REZUMA In reply to replication inter-sites, ...
Collapse -

by REZUMA In reply to replication inter-sites, ...

This question was closed by the author

Related Discussions

Related Forums