Synchronize Plesk Servers (Failover)
Keep two (or more) Plesk servers in sync for a failover scenario.
Migration Manager only allows manual "sync"
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.
Still not started investigating, developping or even started a discussion or planified in this must-have feature ? Since 6 years this suggestion has been posted ? what the **** ?!
Anton Kikels commented
Yes! HA Clusters are in the 20th century a must have for Internet-Services!
I would like to add to plesk panel that I can install webpage on two or more server and a page will be loading from multiple servers on diffrent location
Adam Skarżyński commented
Yes! needed it.
It's really a must have feature nowadays. Could you write some lines about your plans, please?
Jay Krishna commented
calonge.in webmail server failure
Please can we have this. We use Plesk on KVM and would be ideal to have HA without having to manually copy KVM images across
Andrea Lugli commented
Add the ability to to setup Plesk for High-Availability inside Google Cloud Kubernetes Engine
Thibaut l commented
I propose two things for the load balancing
1. Load balancing in case of server overload
In the case of a server traffic overload for example, it would be interesting for the load to be balanced on one or more other servers while keeping all the features and a common database. Thus the user can continue to use the services even in case of attack by DDOS.
2. Load transfer in case of failure
If server A fails, server B takes over.
Constantinos Lyras commented
Is a must feature.
The real need is for a suppported High Availability configuration.
What is really needed is a supported configuration that can make use of other proven technologies like load balancers, clustered file systems and clustered databases
John Pierre Haase commented
??? need this function
Its been long waiting. Is it available in cpanel?
To be honest, I can't understand why Plesk hasn't yet found a useful and consistent solution to this problem. Nowadays this should be standard, especially as market leader in hosting administration!
I very much hope that the feature will be implemented soon, because meanwhile 5 years have passed since the first request!
Mauro Cappuccio commented
Can be really usefull!
Hayden Hoke commented
This is my number 1 wanted feature for reliability and resiliency for larger customers. I thought they were going to accomplish it with the Plesk Multi Server extension but they abandoned that product.