Applicable to:
- Plesk Obsidian for Linux
Symptoms
-
Migration performed from Plesk 18.0.27 or lower to 18.0.27 version failed with the following error:
PLESK_ERROR: Failed to import backup dumps to target panel’s repository
Cause: Failed to import backup XML: errcode must be ‘0’ (no errors) or ‘116’ (backup sign error).
Output of pmmcli utility:
<?xml version=“1.0” encoding=“UTF-8"?>
<response>
<errcode>119</errcode>
<errmsg>Unable to import file as dump: Import error: Unable to find archive metadata. The archive is not valid Plesk backup or has been created in an unsupported Plesk version</errmsg>
</response>
That is a critical error, migration was stopped. -
Additional Apache/nginx directives are not migrated with the following error:
PLESK_ERROR: Failed to transfer additional Apache/nginx directives
Migration tools tried to perform operation in 3 attempts: Command LANG=en_US.UTF-8 ALLOW_WEAK_PASSWORDS=1 PLESK_RESTORE_MODE=1 backup_restore_helper --restore-subscription example.com -ignore-nonexistent-options failed with exit code 1:
stdout:
stderr: Unknown command: --restore-subscriptionNote: The above error is shown after updating to the new Plesk Migrator version v2.19.4
Cause
Bug #PMT-4781 has been fixed and migration is now possible.
Resolution
To fix migration error, update Plesk Migrator extension:
Comments
37 comments
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
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
Seems to be working now. Thanks.
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.
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
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
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,
Please sign in to leave a comment.