• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question MariaDB: different versions on localhost and remote. Bad idea or not?

janpieterk

New Pleskian
Server operating system version
Ubuntu 20
Plesk version and microupdate number
18.0.79
Hello,

Plesk Obsidian 18.0.79 on Ubuntu 20. MariaDB on localhost: 10.3.39.
Sites use an external databaseserver by default: Ubuntu 20, MariaDB 10.3.39.

If the external server gets a release-upgrade to Ubuntu 22, its MariaDB will be 10.6. It would then be different from the version on localhost, which can either stay on 10.3 or be upgraded to 10.11 from the Plesk interface. In boh cases, the localhost DB will be a different version from the remote. Would this be problematic?

Any ideas or tips? Thanks in advance.
 
Upgrading your remote database server should likely not cause you any issues. It's fine to run different MariaDB (or MySQL) releases on remote server. It's actually one of the great use cases for the remote database feature.

I also want to point that if you're still running Plesk on Ubuntu 20, you might want to consider upgrading or migrating to a newer OS for your Plesk server too. As Ubuntu 20 officially reached End Of Life status back in April of last year and is currently only supported trough Extended Lifecycle Support.
 
Thanks for your reply, and good to know that a newer version of a remote db won't be a problem.
Ubuntu 20 on our Plesk servers will be upgraded, in the meantime we have extended support enabled.
 
Back
Top