Synchronize Plesk Servers (Failover)
Keep two (or more) Plesk servers in sync for a failover scenario.
Migration Manager only allows manual "sync"
Ralph Keck
shared this idea
Although the implemented solution differs from the initial demand, we are closing the request as "already available”. We have thoroughly investigated the idea to solve the redundancy issue using a Plesk cluster. Our research has proved that this solution is not in step with the times, is no longer demanded by our partners, and has its limitations. We would like to give an explanation of each point.
More than nine years ago, when the request was created, the IT world had already begun to change. Previously, partners and customers bought or rented bare-metal servers and organized them in data centers. If the servers did not have sufficient component redundancy, there was a risk that a power supply or hard drive failure would lead to service downtime. However, a synchronized failover server could save hosting from such problems. But since then, hosting infrastructure has changed significantly. These days, public clouds are everywhere, partners and customers use virtualization systems, and software runs in containers.
We interviewed our partners to make sure they still needed a high-availability (failover) cluster for Plesk. It turned out that the majority of partners already had virtualization systems in their infrastructure. To protect a server with Plesk from failures, many partners already use high-availability features provided by virtualization systems. Some partners are no longer interested in a high-availability (failover) cluster. Instead, they would like to have a high-load cluster with active/active nodes, where the load is balanced between all cluster members.
In the meantime, we tried building a Plesk cluster. It proved to be possible but with many limitations. A Plesk cluster also requires more servers and resources for deployment from partners and customers, which leads to increased infrastructure costs. The solution would be unreasonably expensive for end users. Developing a Plesk cluster further and making it suitable for production requires lots of additional investments. They will not justify themselves from the point of view of our partners, customers, end users, and Plesk itself. Should anyone decide to continue the research on how to adapt Plesk to be a part of a failover cluster, we have published our research results together with the proof of concept. If you have any feedback, we have created a topic about high availability Plesk on our forum.
Note: We recommend using a centralized database and centralized file storage (NFS) together with virtualization systems and/or cloud providers that provide high-availability functionality on the server rather than the software level. At the same time, we do not plan to continue developing any high-availability redundancy on the application level.
— AY
-
Kamil Macieja
commented
A Datacenter just burned down.
I woud be Happy if we coud have an HA ontop of HA infrastructure.
-
Hostasaurus
commented
HA works great until your data center burns down; i.e. OVH earlier this week.
-
Kamil Macieja
commented
It woud be cnce if you coud buy for proper money kind of an HA Setup With Master and ***** Nodes.
Yes HA on Proxmox / VMware or what ever is nice but anyways since datacenter still can burn down or whatever it woud be nice if you woud have a HA Setup ontop of your Infrastructure!
Sending Regards from Frankfurt.
-
Shane E
commented
Exactly that, we are on the verge of ditching Plesk entirely due to this one missing feature as we can no longer risk the uptime of websites due to the lack of reliable failover
-
Anonymous commented
Then what about software failure that HA doesn't account for?
-
Anonymous
commented
I have the feeling this should not be done by plesk.. Run your plesk server in a Virtual environment with HA..
-
Anonymous
commented
like
-
Kamil Macieja
commented
Woud be Amazing!
-
Hostasaurus
commented
Plesk seems to be mostly interested in clients who just want to spin up a VPS and put wordpress on it for $5/month. I don't think this feature, or any other feature important to a high availability / enterprise customer, will see much development time from them these days.
-
Vaclav Elias commented
Just a reference for Ralph's comment and for Plesk team if they need some ideas :)
-
Ralph Keck
commented
I raised this feature request seven years ago. Many people contributed thought and comments to this. In the whole time, there had been exactly 2 (two) answers from Plesk team. You find me speechless! I cannot understand, why Plesk ignores so many customers' wish.
There are useful tools like unison, dovecot replication and mysql master-master replication, that should be enough to fulfil most needs. And they are free...
For me, I found out, that other mothers do have beautiful daughters, too... I found my luck with ISPConfig and those above mentioned tools. It works and is reliable enough.
Thank you all for supporting my idea!
Ralph
-
Anonymous
commented
Yeah, it’s a shame that it takes so long...
-
There are open source alternatives if I am right, not sure what state they are at the moment. I guess they don't have yet any sync implemented as well. I think this kind of community/open source version would require also donations so the core developers are motivated or even working full time on this and so there is a traction on the development.
Another alternative is to get existing 3rd party Plesk Extentension developers create such extension and maybe raise some money for it. I don't really know what complexity is needed but if everyone who voted here donated $20 for that cause that could be enough budget if I am not wrong?
In any case, it is a fail to not communicate with this community and explain the state of this request regularly, or explain a complexity why it cannot be done at the moment.
Same for the .NET Core/NET 5 request.
-
Anonymous
commented
Anyone want to start a community version of plesk/cpanel using technologies like gluster fs, ansible/puppet, mariadb galera and of course all the usual stuff that plesk/cpanel has apache/nginx etc... it's been too long for both cPanel and Plesk
-
Houssam Chergui commented
It will be done when we have our first Colony in mars :)
-
Anonymous
commented
2013 - 2021 now. will be completed in 3013?
-
Phi Nguyen commented
Any news about the Plesk feature request for HA (High Availability) Cluster and LB (Load Balancing) Cluster ?
-
Sam Thacker
commented
Hey, everyone anxiously following this request: I just found a reply from a Plesk staff member regarding this issue from December 1, 2020 on the forums. They acknowledge that they are "unfortunately late" in implementing this, and have a plan and strategy, but can't talk dates just yet according to the post: https://talk.plesk.com/threads/ha-high-availability-cluster-and-lb-load-balancing-cluster-for-plesk.358980/
-
Daniel
commented
Hey guys,
to be honest. Nobody at plesk will answer. This product is still shut up and give me your money. The only solution is to skip this product. For today there are many other solutions, yes not that convinient, but working, with an active community.
So, one server left, will be plesk free by end of the year, saving a lot of money and have all I ever needed. from plesk
-
Fabio Perri
commented
Hi dear Plesk Team,
Any news about the Plesk feature request for HA (High Availability) Cluster and LB (Load Balancing) Cluster ?
This feature request on Plesk Uservoice it is the most requested and voted in absolute, in fact it is in place number 1, have over 1237 votes, over 151 comments and was created on 31 December 2013 so over 7 years and 11 months ago (also on March 10, 2020 you also created a survey for this feature request) !!!
How is it possible that the Plesk Team failed to implement it in over 2890 days (almost 8 years) ?
I can understand that it involves a fair amount of work and many changes in Plesk but almost 8 years of time seems more than enough to implement this feature request, also considering that Plesk is not free and also costs a lot, you should offer more to your paying customers.
After nearly 8 years of waiting, over 1237 votes and over 151 comments, it would be much more serious of you to make it clear that you will never implement this feature request !!!
I look forward to receiving an official and definitive response from the Plesk Team here.
Thanks in advance for the support.