• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

database cluster recommendations

B

benbroad

Guest
We are building a fault tollerant server setup. I know that plesk can't cope with database clusters so our plan as it stands is:
1. Use round robin DNS
2. leave plesk running on MySQL
3. Use a secondary database system for the actual site databases

The theory being that if one of the servers goes down then round-robin will enable people to be able to see the sites on the second server.

The main issue is database integrity. We are looking at running the sites themselves off PGCluster (PostGRE) anyone have any thoughts on this?

Kind regards,
Ben.
 
Back
Top