Search Engine: Elastic

Article ID: 129281, created on Aug 20, 2016, last review on Sep 1, 2016

  • Applies to:
  • Plesk Automation 11.5


How to add a new node that has MySQL 5.6 to Plesk Automation?


In Plesk Automation update 18 was introduced new service node role MySQL 5.5.

A MySQL service node can be added to Plesk Automation two ways: via adding new service node with the role MySQL/MySQL 5.5 or as external database server. According to the product documentation, the latest version of MySQL supported by Plesk Automation is 5.5 for both scenarios:

At this moment MySQL 5.6 not tested with Plesk Automation and officially is not supported.

However, you can try adding MySQL 5.6 node as external database server following steps in the product documentation:

(scroll down to "Registering an Existing Database Server").

Please pay attention to the following part:

When registering an existing database server, the system does not add it to the list of available service nodes and does not automatically assign any provisioning attributes to this server. This server will be shown only in the list in Infrastructure > Database Servers.

Note that these database servers cannot be configured for automatic service provisioning. To use such a server for providing database services, you should assign its IP address to the corresponding MySQL database or PostgreSQL database resource type of a certain service template. This should be done in Products > Service Templates > select a template > Resources tab > select the MySQL database, PostgreSQL, or Microsoft SQL database resource type > Activation Parameters > Edit.

So technically, you can add MySQL 5.6 service node to your environment with the below steps:

  1. Install MySQL 5.6 on a separate server
  2. Register it as an external DB MySQL server at Infrastructure > Database servers
  3. Create new resource (i.e. MySQL 5.6 database) at Products > Resources and specify MySQL 5.6 server IP address in the activation parameters of the resource
  4. Create new service template with the new resource, so the subscriptions created with this service template will have MySQL service provisioned to the MySQL 5.6 server

Alternatively, you can do in-place upgrade of the existing MySQL 5.5 server, but you will need to change the provisioning attribute of the node and create a corresponding resource type (and new service template with this resource).

Known issues with MySQL 5.6 at this moment:

  • Unable to backup a website with a MySQL 5.6 database via Backup Manager in CCP
  • Unable to create a copy of a MySQL 5.6 database in CCP > Databases

The backup/copy issues are caused by incompatible MySQL client tools (mysqldump utility) which are usually have version 5.0 or 5.1. You can find more details in the KB128721

The compatibility issues above can be resolved by upgrading MySQL packages on the management node to at least MySQL 5.5 version, however this action is potentially dangerous and may cause a corruption of a MySQL databases running on the management node. Therefore we do not recommend upgrading MySQL on the management node.

If you decide to upgrade MySQL on the management node, the following actions are strongly recommended:

  • all MySQL databases running on teh management node must be backed up
  • PostgreSQL database plesk must be backed up
  • full server backup/snapshot of the management node is strongly recommended

See also:

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079 0f0c16f5b0ad439b029f1a4ef76c7eed

Email subscription for changes to this article
Save as PDF