I haven't seen much docos on ADLB. I was one of the guys
who was "beta" testing it back in W2K days though and found my share of bugs.
The bugs I ran into were all around the connections it wanted to delete and then
where it wanted to recreate them to. Basically there were some very bad
decisions because it didn't really differentiate between GC and writeable NCs
and it would try to connect a DC from DOM2 to a GC from DOM1 for the DOM2 NC to
replicate down to the DOM2 DC... Ah yeah that isn't right. :) I was quite
vocal on that problem and it got resolved fairly quickly and the last rev I
ended up playing with (from maybe 2-3 years ago) worked perfectly from what
I saw in a very large unnamed organization.
Use was pretty simple, just follow the adlb /? info. What I
would do is dump the info to LDIF files and NOT commit to the directory so that
I could see what it wanted to do. If you do that for a while and are confident
in what it wants to do, go ahead and have it commit the changes. Or if you
prefer, just run the LDIF files.
Note this isn't something you should have to very often,
just when you see that your connections are getting stacked up on a couple of
DCs and you don't like it. Some people will run it every time they add in a new
DC, others will only do it if they don't like the specific loading. If your
replication latency is fine and you aren't burning a hub bridgehead to the
ground then it is your call if you want to do it or not. My main thoughts in
using it was to lessen the impact of a bad WAN site DC from backing up a
bridgehead's inbound replication. This was a lot larger problem in 2K than it is
in K3 since the timeouts have been reduced for dropping a bad repl partner (or
one across bad WAN links). I used to see occasional issues where a bad network
connection or bad DC could tie up replication for over an hour. This is why I
liked monitoring pending repl queue so much and also why I initially wrote
adqueue (not publicly available) and adqueueloop (on joeware site).
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 12:48 PM
To: [email protected]
Subject: [ActiveDir] Documentation regarding ADLB
My last question was long winded so this one will be much shorter :)
Are there any good resources which discuss ADLB (AD load balancer), how it works? It's issues? How to use it? Etc etc
The branch office guide does not appear to cover this in detail.
Thanks,
neil
PLEASE READ: The
information contained in this email is confidential and
intended for the
named recipient(s) only. If you are not an intended
recipient of this
email please notify the sender immediately and delete your
copy from your
system. You must not copy, distribute or take any further
action in reliance
on it. Email is not a secure method of communication and
Nomura International
plc ('NIplc') will not, to the extent permitted by law,
accept
responsibility or liability for (a) the accuracy or completeness of,
or (b) the presence
of any virus, worm or similar malicious or disabling
code in, this
message or any attachment(s) to it. If verification of this
email is sought then
please request a hard copy. Unless otherwise stated
this email: (1) is
not, and should not be treated or relied upon as,
investment research;
(2) contains views or opinions that are solely those of
the author and do
not necessarily represent those of NIplc; (3) is intended
for informational
purposes only and is not a recommendation, solicitation or
offer to buy or sell
securities or related financial instruments. NIplc
does not provide
investment services to private customers. Authorised and
regulated by the
Financial Services Authority. Registered in England
no. 1550505 VAT No.
447 2492 35. Registered Office: 1 St Martin's-le-Grand,
London, EC1A 4NP. A
member of the Nomura group of companies.
