Multiple remote Apache servers
Planned
As a Server Administrator, I want to have multiple remote Apache servers, so that if a server fails, users will be directed to a working server.
There should be heartbeat setup so that if a server does die the IP is re-routed to an alive server. That alleviates the random-robin complex.
This is a feature that has been migrated over from the cPanel Forums. All previous comments and discussions concerning this feature can be located at:
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Did get this request added to our plan for the product a few months ago, but we don't have it planned for a specific version yet. As soon as we start work on it we'll let everyone know!
Did get this request added to our plan for the product a few months ago, but we don't have it planned for a specific version yet. As soon as we start work on it we'll let everyone know!
@cPanel, was just wondering if this feature is currently being developed or any further updates on this one as its status is planned :)
@cPanel, was just wondering if this feature is currently being developed or any further updates on this one as its status is planned :)
Just for clarification, would the files be hosted on a NAS ? As if the main apache server goes down the backup server would need to be in sync…
Just for clarification, would the files be hosted on a NAS ? As if the main apache server goes down the backup server would need to be in sync…
It might be easier to cluster complete cpanels account with new old technologies like Docker and CoreOS. CentOS7 give also new options. E.g. http://www.tokiwinter.com/building-a-highly-available-apache-cluster-on-centos-7/
It might be easier to cluster complete cpanels account with new old technologies like Docker and CoreOS. CentOS7 give also new options. E.g. http://www.tokiwinter.com/building-a-highly-available-apache-cluster-on-centos-7/
Any chance of having some more info about what's planned here ?
Are we talking about having two cpanel servers and one adding vhosts to the other and vis versa ? If this is the case it would be great, we could have a high availability storage mounted on both servers and simply move a shared IP accross to the other server in case of failure of the first server.
We could then have two servers both running at 40% of their capacity and if one breaks down have one server running at 80 % of its capacity until the first one comes back.
I'm presuming this would mean that PHP could be run on both servers as well as apache.
All we would need after that is some form of high availabilty mysql cluster and the only downtime would be the time required to move the IP accross
Any chance of having some more info about what's planned here ?
Are we talking about having two cpanel servers and one adding vhosts to the other and vis versa ? If this is the case it would be great, we could have a high availability storage mounted on both servers and simply move a shared IP accross to the other server in case of failure of the first server.
We could then have two servers both running at 40% of their capacity and if one breaks down have one server running at 80 % of its capacity until the first one comes back.
I'm presuming this would mean that PHP could be run on both servers as well as apache.
All we would need after that is some form of high availabilty mysql cluster and the only downtime would be the time required to move the IP accross
I noticed this request after commenting on a similar feature request. This really is a core necessity in my view, but it would be great to know what exactly is planned ..
For us either the heartbeat implementation or having a frontend server that routes requests to a main/backup server would complete our needs.
I noticed this request after commenting on a similar feature request. This really is a core necessity in my view, but it would be great to know what exactly is planned ..
For us either the heartbeat implementation or having a frontend server that routes requests to a main/backup server would complete our needs.
We have the possibility of a loadbalanced IP address, We'd defenetly love to have a second server connected to a SAN or NAS storage space so that if one server goes down websites would continue working and so that the load could be shared between 2,3 or more servers.
We have the possibility of a loadbalanced IP address, We'd defenetly love to have a second server connected to a SAN or NAS storage space so that if one server goes down websites would continue working and so that the load could be shared between 2,3 or more servers.
What would be very nice would be to have two cpanel servers, when a user on server 1 adds a vhost' the same vhost be added to the other server.
This way we could mount the same high availability nas on 3 servers and if one cpanel server goes down we could just point the IP to another server that holds the vhosts.
Also sites with their own ip could be migrated like this instantly.
Maybe some form of hook that upon any vhost modification would apply the same change to any other cpanel servers in the cluster.
In our oppinion, the technology used for file storage and for distributing visitors accross servers should be up to each host (load balancing ip, haproxy etc. and nas/san or cerph/glusterfs or even rsync...).
What we rearly want is for each cPanel server to have a role, apache/php server, email server, mysql server, dns server etc. We can already do mysql and dns, there is a feature for emails, just missing apache.
What would be very nice would be to have two cpanel servers, when a user on server 1 adds a vhost' the same vhost be added to the other server.
This way we could mount the same high availability nas on 3 servers and if one cpanel server goes down we could just point the IP to another server that holds the vhosts.
Also sites with their own ip could be migrated like this instantly.
Maybe some form of hook that upon any vhost modification would apply the same change to any other cpanel servers in the cluster.
In our oppinion, the technology used for file storage and for distributing visitors accross servers should be up to each host (load balancing ip, haproxy etc. and nas/san or cerph/glusterfs or even rsync...).
What we rearly want is for each cPanel server to have a role, apache/php server, email server, mysql server, dns server etc. We can already do mysql and dns, there is a feature for emails, just missing apache.
Any update on which version this is planned?
Any update on which version this is planned?
4 years later, is there an update on this timeline?
4 years later, is there an update on this timeline?
Hi. This feature has been tagged as "Planned" apparently many years ago... Should this be corrected? Or is there any real plan to implement it?
Hi. This feature has been tagged as "Planned" apparently many years ago... Should this be corrected? Or is there any real plan to implement it?
Is this still happening? Multiple clients looking for this. There other ways but a native cPanel method would be great.
Is this still happening? Multiple clients looking for this. There other ways but a native cPanel method would be great.
Replies have been locked on this page!