We want to use AD as a regular LDAP for storing and accessing our application data in fast and reliable way. We have two physical server and want to organize some sort of clustering for AD and its data. What is the best-practice for such task?
SnapOverflow
AD is already clustered. You bind to the domain using the correct entries that AD has stored in DNS. Edit - to clarify :
You don't do anything to cluster AD. The process of dcpromo to make a server a DC will automatically make the new DC take part in AD replication. That keeps the AD database synced. You don't need to do anything to make you application failover-aware either; you bind to the domain, not a single serve
Having said that, it's not a great idea to store much of your own data in AD's schema. You may want to make your own partition, or use LDS (formerly ADAM.)