Unable to perform migration: Unable to find archive metadata. The archive is not valid Plesk backup or has been created in an unsupported Plesk version

Follow

Comments

37 comments

  • Avatar
    Anton Maslov (Edited )

    Alejandro Betancor the latest one should be v2.19.4, could you please try to check for update one more time?

    Extensions > Updates > Check Now and update Plesk Migrator to version v2.19.4 

    0
    Comment actions Permalink
  • Avatar
    Markus Plänitz

    After i got the first two errors which are gone with 2.19.4 now there is a new one: 

    Failed to synchronize subscription with plan
    Migration tools tried to perform operation in 3 attempts: Plesk error [1002]: Argument 3 passed to Db_Table_Row_PhpSettings::getConfigurationText() must be of the type string, array given, called in /opt/psa/admin/plib/PHostingManager/Apache.php on line 289

    0
    Comment actions Permalink
  • Avatar
    Erik Blazynski

    Seems to be working now. Thanks. 

    0
    Comment actions Permalink
  • Avatar
    Adam Janiec

    Hello,
    It seems the very same error pops up when generating backup to remote storage (ftp). The actual backup is generated, but it cannot be verified by Plesk.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello,

     Markus Plänitz

    This looks like a bug PPPM-10907, fix for which was released on the 12th of May. Do you have the most recent Plesk Obsidian update installed?

     

    Adam Janiec

    There's a possibility that backup is being modified somehow on the FTP server or you were affected by already fixed bug: https://support.plesk.com/hc/en-us/articles/360035137874

    0
    Comment actions Permalink
  • Avatar
    Markus Plänitz

    Hi, 

    yes i saw this bug later and decided to change all those old settings of http / https folders so i got around that bug. 

     

    Thanks, 

    Markus 

    0
    Comment actions Permalink
  • Avatar
    Adam Janiec

    Hi,

     Markus Plänitz

    This looks like a bug PPPM-10907, fix for which was released on the 12th of May. Do you have the most recent Plesk Obsidian update installed?

    I've been running the latest version. This started to happen on newly migrated server (clean install).

    Cheers,

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request