ADAM High Availability

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We're in the design phase of a project which will replace multiple eDirectory
servers at a single site with ADAM servers. The eDirectory servers currently
sit behind a network load balancer. The project requirements are such that
instead of having just one ADAM site, we'll also be adding two additional
sites which minimally contain at least 2 ADAM servers each.

What we are trying to accomplish is basically this. LDAP requests will hit
the network load balancer reponsible for their geographic region. The load
balancer will try to use the regional ADAM servers first, and if they're not
available, route out to ADAM servers in the next closest site, then the next,
and so on.

I haven't been able to find much documentation on ADAM being deployed in a
multi-site configuration. Eric Fleischman's blog posting has some basic
information regarding ADAM high availability, however I need more information
about how well a multi-site design will work in practice.

Here's a link to Eric's posting:
http://blogs.msdn.com/efleis/archive/2004/10/07/239102.aspx

Thanks in advance,

Jason
 
To answer my own question...

After some further investigation by our team into using just network load
balancing to support ADAM high availability across multiple sites, it has
been determined that we'll also need to utilize an LDAP proxy server such as
OctetString's VDE to support our needs.

Jason Raneses
 
Thanks for following up, there's very little information around
about what people are doing in ADAM deployment so it's
interesting to hear.

Thanks!
Lee Flight
 
Back
Top