Re: AD Lag Site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Tim Chin" <donotemail> wrote in message
news:ubk6dCkkHHA.208@xxxxxxxxxxxxxxxxxxxxxxx
Thanks, everyone, for your posts. You had some very good information. We
will continue to pursue the 'lag site' concept as it requires no
additional hardware in our environment and will give us a convenient
option in the event of a restore.

Ok, but why the lag? Why not just keep it (reasonably) up to date?

Wouldn't at least nightly be better?


Thanks again.

--
Tim

"Brian Desmond [MVP]" <brian@xxxxxxxxxxxxxxxx> wrote in message
news:OOolnQOkHHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
You would want to assign that DC to the site - create a /32 subnet, that
is make the subnet the IP of the DC and the mask 255.255.255.255.

The cost is irrelevant unless there are multiple site links connecting to
this site.

You need to actually disable inbound replication with repadmin to really
do this -
http://technet2.microsoft.com/windowsserver/en/library/03b7fc47-e25c-4af8-822f-f856b565b76a1033.mspx?mfr=true.
You'll want a automated process (e.g. scheduled task) to do this.

Just setting the interval to be large won't prevent urgent replication
and such.

The other way to do this is to put it on a subnet behind a firewall and
use a timed firewall rule.

--
Thanks,
Brian Desmond
Windows Server MVP - Directory Services

www.briandesmond.com




.