none
ADDS Site Topology Question RRS feed

  • Question

  • Hey guys,

    We have a single domain forest with 11 sites in our domain.  Our sites have pretty fast and fault tolerant network connections, but we do have a single domain controller in each site just in case a circuit were to go down.  Our site connections are set to IP for transport.  We do have one central site with the fastest connections and (2) Domain controllers in it.  With decently fast connections, what is the best topology to use?  Should I just use a hub&spoke connection to the fastest central site or should I use a ring topology?  Does Micrsoft recommend mutiple site connections in a hub&spoke topology for better fault tolerance?  I know this stuff is dependent on several factors, but our connections are pretty fast and I am just looking for some info on what is the most simple and Microsoft recomended way of connecting our sites.

    Thanks,


    Dan Heim

    Thursday, April 28, 2011 10:28 PM

Answers

  • I'd go with hub and spoke in this case.  Create your HQ site and then the 10 remote sites and create site 10 site links

    HQ to Remote1

    HQ to Remote2

    and so on

    Let the KCC/ISTG do its job and create the connections for you.  If you find that is not adequate down the road you can change that but start with KCC.

    I'd also make every DC a GC in this setup.

     

    Thanks

     

    Mike


    http://adisfun.blogspot.com
    http://twitter.com/mekline
    • Marked as answer by DaveBryan37 Friday, April 29, 2011 3:14 PM
    Friday, April 29, 2011 2:29 AM

All replies

  • Hello,

    i would go with the default created connections, especially as speed is not to take care about.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, April 28, 2011 10:49 PM
  • I'd go with hub and spoke in this case.  Create your HQ site and then the 10 remote sites and create site 10 site links

    HQ to Remote1

    HQ to Remote2

    and so on

    Let the KCC/ISTG do its job and create the connections for you.  If you find that is not adequate down the road you can change that but start with KCC.

    I'd also make every DC a GC in this setup.

     

    Thanks

     

    Mike


    http://adisfun.blogspot.com
    http://twitter.com/mekline
    • Marked as answer by DaveBryan37 Friday, April 29, 2011 3:14 PM
    Friday, April 29, 2011 2:29 AM
  • Hi Dan,

    While creating the topology AD will try to reach the other servers in 3 hop limits. Consider an example below.

    Server A - First DC in domain A 

    Server B- Second DC in domain A[ built using reference with Server A] . Here, Server A will have one incoming connection for server B and Server B will have one incoming connection for Server A

    Server C- Third DC in domain A [ built using reference with Server B]. Here, Server C will have one incoming connection for Server B and server B will have one incoming connection for Server A.

    Server D - Fourth DC in domain A.[ built using reference with Server c ] Here, Server D will have one incoming connection for Server C and Server C will have one incoming connection for Server D.

    By now,  while replciating the changes, server D will come to know that  its replication partner Server C is also reciving updates from another Server[ Server B]. Now server D will try to see if a connection can be made directly with the server B. Once finalised, its possible and yes. the connection between the Server B and Server C would be removed. a new connection between server B and D would be established. This is to make sure any servers in domain are reachable within 3 hop limits.

    So, KCC will automatically take care of your request and will decide what's best for you. Manual intervention is not at all required.

    So, the hub and spoke connections will be made when there is a 10 th DC in your site. you hav 11 sites - 11 DC's and one site with 2 DC. That will become 12 DC's. So you will automatically recieve hub and spoke replication topology in your environment ,which is the best for you as decied by KCC.

    Hope this helps..

     


    Regards, Mohan R Sr. Administrator - Server Support
    Friday, April 29, 2011 2:36 AM
  • I would go with Mike, Hub & spoke topology is better. Neither disable KCC nor Bridge all site link objects(BASL), BASL is enabled by default & let it be. Configuring replication based on site cost is better option. KCC generates the replication topology based on various parameters.

    Create the site link with different site & control the replication preferences using site cost.

    Check the below & inside previous discussions link, which surely going to help you.

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/626ded46-6b17-4986-ac26-c71c1c7bb791/#8110f3c6-1e05-410f-aa1f-0bc8bafa3ae6

    Few more references.

    http://searchwindowsserver.techtarget.com/tip/Best-practices-for-Active-Directory-replication-topology-design

    http://technet.microsoft.com/en-us/library/bb727085.aspx

     

    Regards


    Awinish Vishwakarma| MY Blog

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Friday, April 29, 2011 10:03 AM
    Moderator