Hi there,
I'm running a setup with a Heartbeat/DRDB cluster with 2 nodes and open ldap database stored inside the DRDB-device. No problem with the setup itself, it runs perfectly. But I'm having following problem: How to update LDAP in a cluster? The plan was to first run the update on the current slave device, then manually failover and run update on the other device. This was a very bad idea as LDAP needs to have access to its database and as the slave has no mounted drdb-device, it fails and update stops. So is there any recommended update startegy or guide on how to update LDAP inside a heartbeat/drdb cluster? As the LDAP server needs to be online any downtime would be very bad. I'm having some ideas on how to solve this problem but I'm not sure if this is the real solution: Situation: node1 is running heartbeat/drdb with ldap server up | node2 is in slave mode - Stop heartbead and drdb on node2 - Start ldap server with an empty database on node2 - Update ldap and everything else on node2 - After successful update stop ldap on node2 - Start Heartbeat/drdb on node2 - Manual Failover -> node2 now master, node1 slave - goto node1 and redo according steps I hope you understand my concern and you can help me to fix this update-mess. Is anyone out there with a solution or do you guys just handle it like 'hitchhikers guide to galaxy' advises? (Asking Hitchhikers Guide: How to Update LDAP in Heartbeat Cluster? - Don't! http://www.imdb.com/title/tt0371724/quotes?qt0351093 ) Greetings from Germany, Christopher Metter _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
