Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Complete High Availability System

ayi

I'm in the process of configuring a LAMP server but want to make sure it'll be ready for expansion for the future.

Here's my current setup..

Two physical windows servers clustered with Hyper-V
Two virtual machines, one for Apache and another for MySQL
Two Synology ISCSI luns configured as a RAID5, one for Apache and another for MySQL
Each virtual machine is setup to use their respective ISCSI as the data folder

(website data for apache and database data for mysql)

Here's what I want to do..

Second Apache server configured as a failover (active-passive)
Second MySQL server configured as a failover (active-passive)

Here's where I need help..

My thinking was to use a virtual ip address, which would be assigned to one of the two apache servers configured as a master. If the master dies, I want the secondary slave server to claim that virtual ip and act as the master until the original master comes back online. I don't have to worry about syncing data between the two apache servers since the data is being stored in the ISCSI. I don't have to worry about "file-access-conflict" since only one of the servers will access the server at a time. This same concept applies to the MySQL servers.

The question is.. Do you think this setup stands good for now and the future. The next question is.. What should I use for the active-passive failover handling. I was looking into ucarp, which seems pretty easy to use. What do you guys think?

ayi

If you do have just one Synology box shared between your Hyper-V machines, it can still be considered as a SPoF. It dies, you lose all the LUNs sitting there. For true HA you would need a second NAS box and some replication mechanism. Well, one thing that comes to mind is HA cluster with two Synology NAS devices. But AFAIK it doesnt rate well in the world of HA. Especially because of performance and slowness of failover. So mostly we usually lean toward some of SDS solutions like HPE VSA (http://www8.hp.com/us/en/products/data-storage/free-vsa.html), Unity VSA (http://www.emc.com/products-solutions/trial-software-download/unity-vsa.htm) and StarWind vSAN (https://www.starwindsoftware.com/starwind-virtual-san-free). I personally was playing around StarWind a lot and got all the things done very quickly. Their free version should be able to mirror your NAS boxes converting all the stuff into a full fledged virtual san. And finally I wouldnt use Synology for production tasks. It can flawlessly handling a backup jobs, but I doubt it is completely suitable for virtualized environments. So if I were you, I would leave Synology as a backup repository, load Hyper-V hosts with the local disks and create a storage pool wit help of one of the SDS mentioned above.