Hello, After read the manual and some howto I must say that all ok but I have two questions I will set up a cluster with: - ispconfig in mirror mode - nfs, unison, gluster or rsync for mail and web - master/master replication for mysql - heartbeat/keepalived for failover etc 1- Should I select mirror in ispconfig if I use master/master replication? 2- When a server go down (i.e server A) how do dns to resolve to server B (i.e A records from sites)?? Thank you
1) Yes. But be carefully to follow the naming conventions for the ispconfig database and the master/master mysql setup as described in this guide: http://www.howtoforge.com/installin...tabase-cluster-on-debian-6.0-with-ispconfig-3 Especially that the ispconfig databases and mysql users on both servers are different so that they dont collide with the mysql master/master replication. 2) There are several possibilities to achieve failover switching on linux. You can e.g. use a loadbalancer siftware for that (if you use the cluster with two active node) or you use a software like heartbeat that switches the IP addresses from one server to the other one without the need to change dns recods. Changing dns is too slow for many cases, but depending on your needs dns might be ok as well.
Great tutorial Till thank you. In case of failure in the master server will unison sync all new changes in the slave server to the master(sites and mail)? (i.e after hours of failure in the master server) In this tutorial load balancing exist or this setup can be used for obtain this goal? Cheers!
Yes, unison is a two way sync tool. Basically it works like rsync, just in both directions. Loadbalancing is not in the scope of the setup as a loadbalancer is normally one or more external servers or hardware appliances or just dns settings that sit in front of the ispconfig cluster. I've described options in answer 2 above.
