Hi, I'm new to heartbeat, just started to read about it a week ago. I'm using ubuntu, I installed heartbeat 2.1.4 in my two nodes. Here is ha.cf of them:
logfacility local0 keepalive 2 deadtime 5 udpport 694 bcast eth5 auto_failback on node node1 node node2 And here is haresources (I'm testing only apache, the ip address don't matter): node1 apache2 I stoped heartbeat service in node1 and then apache started in node2 , then I started heartbeat service in node1 and apache started in node1 but stayed active in node2. Shouldn't the one in node2 be stopped? Another question: If I stop apache service in one node it don't start in the other node, shouldn't it be started since apache is down? How heartbeat monitors the process to see if it is down or up? And another question: I'm used with VMware HA for High Availability between VMS, it saves a copy of the vm and start it in case of the main one goes down, the vm's data are syncronized between each other. My objective when I started to read about heartbeat was to achieve this same goal but with physical machines, but with some research I realised that heartbeat don't do this alone, I need another software to syncronize data between the nodes. What I want to ask is wich one is the best to syncronize ALL data between the 2 nodes including data that may be in use, data related to hardware (my two nodes have the same hardware), in a way that one node is the mirror of the other just like in vmware HA. Or maybe heartbeat isn't the right solution for this goal? I've heard about LVS for ha and load balancing and Linux HPC and I was thinking about some hardware stuff too. One more question: I've read somewhere that you can have a "heartbeat server" used to manage the multiple pairs of nodes, is this right? Is there a gui for this like a web interface? Thanks. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
