The best way to minimize the amount of replication traffic is by centralizing your Domain Controllers. Have you considered the possibility of not placing any DCs in location 3?
The 3rd site is for disaster recovery, so we need to have local DC's there if only for that.
This topology has the following benefits:I originally planned to allow replication to occur 24 hours a day to allow for shorter convergence time possible. But your suggestion does have some benefit that we'll have to consider.
* Changes are replicated only once (most of the time) from and to s3 because s1 and s2 replicate more frequently and will keep each other up to date. So changes send from s3 to s1 will not be replicated again from s3 to s2 because s1 has already send the info to s2.
HOWEVER ... I would strongly recommend to seriously consider the most simple alternative. Implement s3 and "connect" this one to the default sitelink.
This will effectively make a full mesh type configuration, right? We aren't too afraid of over-utilizing the link to Site 3, but we still want to limit traffic wherever possible. However, am I really saving anything by establishing a second site link with a higher cost with just 3 sites?
List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
