Plesk cluster setup

However, I found that the domain information created under the admin interface is not updated after failover to the other server.

Where is the domain information stored during domain creation in admin interface? Is it stored inside mysql or other database directory. I need to move this information to the shared drive in order to make the cluster works. It'll be in the "psa" database of your normal database server so in the stock MySQL data directory Good luck with what you're trying to accomplish. How about postgresql?

Does Plesk use any info from Postgresql? After machine fail-over, these information will lose. Need to find out method to continuous copy changes of these two files to the standby server. Any method to make change of the creation of ftp users to mysql or ldap? Why Plesk is not setup to work in Cluster environment??? There are no any system Plesk information in Postgresql database. It is used only for client's databases. It is very interesting question about running Plesk in cluster environment.

As I see you have performed some useful tests. I will forward your idea and results to developers and management to the further investigation and discussion. Could you please describe with details what was done and what is encountered problems? Hi all, First, my plesk cluster only used for Web Hosting service. We are not using Mail and DNS. I have setup two Linux servers running Redhat Cluster with a common disk storage.

When the server failover to the other server, the httpd can not startup as it will look for the ftp account information. I have wrote a script to solve it. Question Hi, I want to do the same, does your cluster works fine? Since how many time? Hi, Sorry for late reply! We have used the Plesk in cluster environment for our Web Hosting users. However, we only provide Web Hosting and no email or dns functions. In several cases, the fail-over success but it fail times.

As I mentioned, I rely on the mysql db which store user password to recreate user. I have reviewed the case where the user or password does not exist in the mysql db which cause failover not working. Now Plesk will offer the clustering through there new product www.

Kind of - it still wont offer clustering of web customers or the panel itself. Its really just mail, dns and DB which you could have already done anyways with a little work. Until they actually get true clustering web customers mostly but the panel as a close second it may not be worth it for a lot of people. Your Amazon instance is billed on hourly basis, starting when it boots up and ending with the instance termination.

You may choose how to pay for the Plesk license:. When the instance is stopped, no hourly usage fees or data transfer fees are charged, however, you are still charged for the storage for any Amazon EBS volumes. Each time an instance is restarted it is assigned new public and private IP addresses dynamically. If you wish to have a static IP address to associate with your instance, obtain an Elastic IP address and assign it to your instance once you create it.

The elastic IP address is associated with your AWS account, so you can assign it to your instance at any time. After assigning an elastic IP address to your instance, the instance must be rebooted.

See Reboot Your Instance for instructions. If you do not with to reboot the instance, there is another way. Instead, you can execute the following commands:.

Note: When an instance is stopped, the elastic IP address is unassigned from it. You will need to assign it anew when you restart a stopped instance.

To log in to Plesk for the first time, you need to generate a one-time login link. Browse the generated URL to log in to Plesk and set an administrator password.

As a workaround;. You can find more information about this bug in here; Zones are not transferred from Bind on Windows. In order to overcome this, rename your DNS records as domain. Your named.