I am running Virtualmin GPL currently, and I am currently hosting around 20 domains.
Right now I just have a single server, but as I host more and more domains, I am looking at trying to get another host to run as my backup in case the main server fails. I am running my main host as a virtual machine (VMware), so what I was planning on doing was to copy my existing server and run it at the second location/host.
I am assuming that I would have to change a few things within Virtualmin/webmin/linux on the second host, plus setup some sort of rsync to replicate any changes made on the main server to the secondary host. DNS would be taken care of by configuring bind to replicate changes to a secondary host.
Would going to Pro help me with getting this setup in a way that it would be a solid failover? The goal in the end is to make it so if my main host goes down, my second host could run everything web/dns (sql too) related at a minimum. Email... I am assuming that I could just set it up to hold the email and pass it onto the main host when it comes back up. Does the Pro version support handling/managing a 'duplicate' fail over host?

I am liking some of the features that Pro offers, such as resellers feature (since pretty much all the domain hosting is setup by someone else, I just run the server), but before I start upgrading my services on the server, I would like to get some more redundancy in place first.

I run a cluster with Virtualmin. The way I do it is to move all shared configuration and user files on a separate NFS cluster thus automated the changes made. I only run Virtualmin on one of the nodes so if it goes down management is impacted. In order to provide the HA services I use heartbeat and locate the mail like services on one node and the web services on the other with cross failover.

I hope this helps.

Same type of configuration here.

I've been pondering how to cluster virtualmin's management interface for high availability and load balancing, but I haven't had a chance to seriously look into it yet.

Can you elaborate on how you managed the clustering using a shared NFS mount? Which files did you put on the shared mount and which other files do you have to eventually keep synchronized?

Thanks in advance!
Niclas

KrisKenyon wrote:
I run a cluster with Virtualmin. The way I do it is to move all shared configuration and user files on a separate NFS cluster thus automated the changes made. I only run Virtualmin on one of the nodes so if it goes down management is impacted. In order to provide the HA services I use heartbeat and locate the mail like services on one node and the web services on the other with cross failover.

I hope this helps.




Hello
If anyone can help me or direct me any resource i will be appreciate for it.I want to use Virtualmin to serve small reliable hosting platform.I want to use clustering use virtualmin .MySQL and mail servers SAN or NFS to storage system .Is there anyone out to help me and maybe someone has got network diagram and similar data and how to set up clustering .Thank you very much.

I'm also interested in this feature for next year (purchasing a second server about then).

But, this is a topic that I think could be a good addition to the documentation wiki.

Could the people who have succeeded in this write up something on the wiki (rather than here)? At that point, we can "trick" Joe and Jamie to support it, since it's on the documentation pages (little joke here).

I know there's some sort of clustering in Webmin, but does it handle Virtualmin files, etc. as well?

I'd like to see this officially part of the package at some point.

Yes, Ive noticed the features in VM for a time, and been trying to find info re: cluster/ing in Wiki, and it doesnt seem to yet be there.

Joe - can you add this asap!?

Can someone provide a list of configuration files that need bo be synced from the master to the slave server?

This would be very useful.

(Bump) I've been looking at this for some time and really hoping that Virtualmin will put together a howto or a plugin/feature that allows users to have a mirrored hot-swap(in the least) and ideally loadbalanced servers. This is something I'll be experimenting with here...

http://www.howtoforge.com/high_availability_loadbalanced_apache_cluster

I'm hoping I can user virtualmin servers and isolate the Virtualmin server's management interface that is going to be the "master" of the cluster...and use rsync scripts or the cluster features of Virtualmin to execute the synchronization between the two servers.

Is this even reasonable? Has anyone tried this sort of thing? I'd like to know if this is a rabbit hole not worth the time...

Unison would be a much better choice than rsync for this. :)

That said, I had started developing the Apache Clustering module and stopped, for lack of time, and apparent lack of interest. If there's sufficient interest I'll look into finishing it...