What are known limitations of Plesk Migrator Extension?

Follow

Comments

11 comments

  • Avatar
    Stéphan Schamp

    Also note that:

     

    - Websites PHP Performance settings seem to get migrated
    - Websites PHP Common settings are NOT migrated, you need to check these if they are still compatible

    This is also valid when switching between different PHP versions (eg. atomic-php56 to plesk-php56).

  • Avatar
    Anton Maslov

    @Stéphan, thank you for the additional information, I'll double check that with developers and update an article with results.

  • Avatar
    Marco Marsala (Edited )

    Beware: Plesk Migrator won't migrate (without notice): MySQL routines, events, triggers, user-specific permissions, event scheduler status

  • Avatar
    Marco Marsala (Edited )

    I think points 10,11,12,13 are easy to implement. 15 and 18 may be handled with some sort of renaming feature, like you already do for databases with conflicting names.

    About point 11, these settings may be migrated if PHP major and minor version match (for example having PHP 5.3.19 on target server and PHP 5.3.21 on destination server).

  • Avatar
    Bulat Tsydenov

    @Marco, Hi! 

    >Beware: Plesk Migrator won't migrate (without notice): MySQL routines, events, triggers, user-specific permissions, event scheduler status
    As for events, they are supposed to be migrated since 2.9.2 version of Plesk Migrator which was released on 07 June, 2017. Refer to Plesk Change Log
    As for stored procedures, stored procedures are supposed to be transferred. Can you please clarify the following information:
    - Plesk and OS version of both source and destination server
    - versions of MySQL on both source and destination servers

    As for user-specific permissions and event scheduler status, can you please provide more details? Do you mean that you set some custom permissions for db user through Plesk interface on source server  and they were transferred incorrectly?

  • Avatar
    Marco Marsala (Edited )

    @Bulat, I retried the migration multiple timesbut the following objects weren't transferred: routines, functions, AFTER triggers.

    Plesk is version 17.5.3 Update #25 on both servers. Plesk Migrator is version 2.11.4-0 on both servers.

    O.S. is CentOS 6.7 with MySQL 5.6 on target server, Ubuntu 16.04.1 LTS with MySQL 5.7 on destination server.

    > Do you mean that you set some custom permissions for db user through Plesk interface on source server  and they were transferred incorrectly?

    Yes, exactly. For user-specific permissions I mean GRANTs you can set from Tools & Settings > Database Servers > phpMyAdmin > User accounts (screenshots: https://snag.gy/5j4OFb.jpg - https://snag.gy/KXseUE.jpg). They weren't transferred at all.

    As for Event Scheduler status I mean the global option you can enable from Tools & Settings > Database Servers > phpMyAdmin > (select a database) > Events (screenshot: https://snag.gy/gkS1ba.jpg). As you know, event scheduler should be enabled when you want to run events, so it's advisable to transfer the value of that setting. Actually, it wasn't transferred.

  • Avatar
    Bulat Tsydenov

    @Marco,

    > I think points 10,11,12,13 are easy to implement. 15 and 18 may be handled with some sort of renaming feature, like you already do for databases with conflicting names.

    > About point 11, these settings may be migrated if PHP major and minor version match (for example having PHP 5.3.19 on target server and PHP 5.3.21 on destination server).

    As for these statements, it would be great if you provide your suggestions how Plesk migrator extension can be improved with your vision how it can be implemented at Plesk Uservoice. The top-ranked suggestions are likely to be included in future product updates.

  • Avatar
    Bulat Tsydenov

    @Marco, I've just checked that in test environment and indeed they were not transferred. I am going to report it to developers.

  • Avatar
    Konstantin Annikov

    @Marco,


    Our development team has investigated the issue and confirmed that it was caused by a product defect. A bug has been created: PMT-4065: Plesk Migrator does not transfer MySQL events, global user privileges, stored routines, event scheduler status. Thank you for bringing this to our attention!

    We will do our best to fix the issue in one of the next Plesk Migrator updates. You may subscribe to this article to be notified when the bug would be fixed:

    https://support.plesk.com/hc/en-us/articles/115003140613

  • Avatar
    Marco Marsala

    @Konstantin this issue affects restore of databases from backups too

  • Avatar
    Konstantin Annikov

    Hello, 

    Thank you for bringing our attention. This is predicted behavior and it will be fixed in scope of the same bug. 

     

Please sign in to leave a comment.

Have more questions? Submit a request