Today I’m going to walk you through how I went about replacing MySQL with Percona. The load on one of my servers reached the point where replacing MySQL with Percona just made sense. The approach used here may seem redundant to some but this is the way I got things to work. We’ll need to upgrade MySQL to 5.5 so the database connector used by Plesk is updated as well, otherwise things might not work. If you haven’t heard about Percona I suggest you head on over to 

A little bit about Percona from their website

First things first, make sure Plesk is up to date, at the time of writing Plesk stood at 11.5.30 Plesk 11.5 updateAdd the Atomic repository to CentOS.

You should see this in the end atomic repo

Next step is to update MySQL, this will in turn upgrade PHP as well. The server I am upgrading was running PHP 5.3 so an upgrade is welcome.

yum mysql php upgrade


Next step is to upgrade all the database for MySQL 5.5

It’s now time you log into Plesk and make sure it’s working properly, to verify this add a new customer. If all goes well you should see a message similar to the one below. Note: test is the name of the customer for the sake of this example.plesk 11.6 mysql working success Here starts the fun part, start by dumping all of the MySQL databases.

Below we’re going to remove MySQL.

This makes sure you only remove MySQL and none of it’s dependencies.

Issue the following to add the Percona repo to your server.

Issuing the following at shell should tell you what’s available through Percona.

percona 5.6 repo add mysql  shell

To get Percona up and running you need three things

  • Percona-Server-Client-5.6
  • Percona-Server-Server-5.6
  • Percona-Server-Shared-5.6

Issue the following at shell to install the client server and shared library.

Start the Percona server.

percona 5.6 started centos php plesk apache



Now check and see whether Plesk is playing nice with it. Again, create a new customer to see whether things run smoothly, if the customer is created then all is good.