04-14-2020 05:28 AM
Hello Everyone,
I am currently working on a IPSK Manager deployment and want to setup some type of HA for the system. I have a primary server successfully working for self registration. I want to setup a second IPSK Manager server for HA purposes and have all users, portals ( I know I might need to build the portals manually) and MAC addresses replicated over to the HA server in case of a disaster. However I want to see about getting two way replication working so that when the primary server is recovered everything will replicate back to the primary server and it can take over. The GitHub page for IPSK Manager references briefly that HA is possible with the built in features of MYSQL. However, I wanted to see if anyone has tried this? Any catches? What type of MySQL replication did you use? Is there a better way? I have been looking into Master - Master MySQL replication. If anyone has MySQL in depth knowledge, is this what I should use? Thank you for any feedback. It will help with assessing my options before trying to deploy IPSK Manager into production.
Solved! Go to Solution.
04-14-2020 11:51 PM
I am going back some years now, but there are two things in play:
For MySQL most folks ended up creating a homebrew solution using Pacemaker and Corosync. The reason this is a homebrew is because in the simplest case there is no centralised storage (e.g. a fiber channel attached storage volume). If you don't have a centralised storage solution for servers SQL1 and SQL2, then you have to replicate tables between them. And Pacemaker and Corosync are used to create a VIP (Virtual IP) that creates the illusion of a cluster. Your application talks to the VIP and doesn't need to care which SQL server is the active one.
It's probably out of scope for this forum but I think there are some more up to date examples on the net.
04-15-2020 05:52 AM
04-15-2020 01:41 PM
The topic of MySQL replication seems to be covered by experts out there and it can be done without any third party ($$$) tools.
see if this link helps?
https://www.toptal.com/mysql/mysql-master-slave-replication-tutorial
04-14-2020 11:51 PM
I am going back some years now, but there are two things in play:
For MySQL most folks ended up creating a homebrew solution using Pacemaker and Corosync. The reason this is a homebrew is because in the simplest case there is no centralised storage (e.g. a fiber channel attached storage volume). If you don't have a centralised storage solution for servers SQL1 and SQL2, then you have to replicate tables between them. And Pacemaker and Corosync are used to create a VIP (Virtual IP) that creates the illusion of a cluster. Your application talks to the VIP and doesn't need to care which SQL server is the active one.
It's probably out of scope for this forum but I think there are some more up to date examples on the net.
04-15-2020 05:52 AM
04-15-2020 01:41 PM
The topic of MySQL replication seems to be covered by experts out there and it can be done without any third party ($$$) tools.
see if this link helps?
https://www.toptal.com/mysql/mysql-master-slave-replication-tutorial
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide