Bug #72199 Steps to upgrade 5.5->5.6 can be confusing

Description:
Created from bug #72187.

"Steps to Back Up on MySQL 5.5 and Restore on MySQL 5.6 " can be confusing if a user uses package manager which does not allow to have two different versions of MySQL server same time.

How to repeat:
See description and comment "[1 Apr 15:45] Daniel van Eeden" to bug #72187

Suggested fix:
Add alternate steps, which does not require to have two versions of MySQL server, but still will work:

1. Back up data on the MySQL 5.5 server.

2. Restore data on the directory you plan to use for MySQL 5.6 server's data by simply running an apply-log and then a copy-back operation on the backup.

3. Restart the old MySQL 5.5 server, using the data directory of the new MySQL 5.6 server as its own data directory.
Note

This is an extra step beyond the normal restore and upgrade procedures, special to the restoration of MySQL 5.5 data to MySQL 5.6 server; with it, the MySQL 5.5 server prepares the data for an upgrade to MySQL 5.6 by performing some clean-up steps on the data, similar to what the server would do during a crash recovery.

4. Stop the MySQL 5.5 server.

5. Install MySQL 5.6

6. Start the new MySQL 5.6 server.

7. Run upgrade steps as documented in the MySQL reference manual on the restored data. Make sure the mysql_upgrade that comes with MySQL 5.6 is applied.

There seems to be little alternatives to having both MySQL 5.5 and 5.6 available to work on the backed up data. However, I am working with the development team to find a solution for situations in which you cannot run both of the servers on the same system.

Made the recommended changes to the MySQL Enterprise Backup 3.9 and 3.10 manuals.