so if the DR domain controller is only set to replicate to 1 domain controller in HQ -- this should be fine ? should it hold any FSMO roles, be a DC.
i would still imagine if the other DC's can't talk to this DC - dcdiag and repadmin would fail or generate errors.
If you set the servers to want to communicate between sites as bridgehead servers, then it will autogenerate site links that fit this topology. Otherwise all of the domain controllers will want to talk to each other. Being a member of the root domain, it will have everything needed to get the root domain back up and running. You might want to consider having a DC for the subdomain as well, as the root domain controller will not contain all information about the subdomain.
From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of HBooGz
Sent: Thursday, August 10, 2006 10:37 AM
To: [email protected]
Subject: [ActiveDir] Replication Topology Explanation..
Hey all -
I have an HQ hosting the forest root domain company.com. I have a child domain off-site connected via T1 and it's site.company.com
The HQ is running windows 2003 R2 std. The site is currently running windows 2000 sp4 but will be upgraded soon.
I have a DR site connected via P-T-P T1. The DR box was recently upgraded to R2 and it was DCPROMO'd into my HQ's domain, company.com.
The DR site DC is only set to replicate with one DC in the HQ. there is an ACL on the DR network that prevents communication from any other host except the one DC at HQ. so the other DC at HQ and the DC at the site can't talk to this DR DC.
is this a healthy replication topology ? i was told that since the HQ DC can replicate to the other HQ DC and the site DC it has all the information needed and only one replication connection from this "main" DC to the DR DC is needed.
could use some feedback on how to handle replication for DR location.
we are using Double-Take but was told it really isn't necessary for an AD box, but i would think communication needs to be open for all servers to communicate to the DR boxes ?
Thanks,
--
HBooGz:\>
--
HBooGz:\>
