In red hat docs you may find some scenarios.
Your approach seems ok. The only question in my opinion is how big
redundancy you need. Lets say that master1 fails. Is this situation
problematic for your datacenter? If yes, then you should consider adding
two more ldap servers. They can act as masters or as consumers - again
depending on your needs.
17 wrz 2012 17:05, "Kyle Flavin" <Kyle.Flavin(a)wb.com> napisał(a):
I'm looking to deploy 389 Directory in my environment to replace
existing iPlanet installation. I would be using it primarily to store
user account data for authentication purposes. I have two physically
separate data centers that I would like to share the same directory
tree. My initial thinking is to setup 389 DS as follows:
-A Master/Consumer in DataCenter A
-A Master/Consumer in DataCenter B
-Replication agreement between both masters, to mirror the directory
tree in both environments.
Does this sound like a reasonable approach? Is there a better way to do
it? (ie: four masters?) Is there documentation for best practices when
setting up 389 DS in situations such as this?
389 users mailing list