Keepalived
Keepalived
I am currently looking into High Availability for my work setup. I am having some problems understanding how to achive that. I have two servers, one running libvirt and a couple VM, the other one nothing much yet.
To achieve HA with keepalived, I would have to setup the exact same VMs under the second server, right? If that's the case, how would I make sure that the "mirrors" stay equal, If for example the master goes down, the backup takes over, some changes are made in a DB and the master knows nothing about these changes.
Maybe I misunderstood keepalived so far, can somebody provide me with an example setup or hints on how to achieve what I want to do?
Kind Regards
g7s
You're viewing a single thread.
If you plan on using this in a production environment, I'd bring in a consultant.
However, I've heard of people in the home-lab sphere use things like heartbeat and drdb. The more nodes the merrier as if you lose connection between the two you'll have a bad time.
I'm working for our department as the only IT-admin, everything runs fine and nightly downtimes for upgrades etc. are fine. However, I want to make it more available. Thanks for the suggestions, I will look into them :)
Other data replication technologies worth looking in to: GlusterFs, Ceph.
Dependent on your db's they should offer replication out of the box.
You can also implement a load balancer, such as HAProxy or Nginx, to distribute incoming network traffic across multiple VMs