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:
-
Go to Extensions > Updates > Check Now and update Plesk Migrator to version v2.19.4 :
Note: If no updates are shown that means that Plesk Migrator has already been updated. The version can be checked in Extensions > Plesk Migrator
Comments
41 comments
In a couple of days !?!. I'm sorry but that's unacceptable. You completely broke the migration. I now have to do a migration of several domains to a new server which is due this week and backup/restore is completely broken.
I've followed your advice to do a CLI manual backup and then restore, I'm doing a perfect backup and copy of the content to destination server, both servers are on 18.0.27 and when trying to restore it says I have corrupted databases so the manual method DOES NOT WORK either !!
Hi, I try upload backup from 18.0.38 to 18.0.38 after reinstallation OS and I receive: "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"
Seems to be working now. Thanks.
Thaks for fix ASAP. Regards.-
I don't understand why I need to use Migrator, I would like to upload a backup from my HD and not migrate data, for me these are two different activities. The message appears when I use the Backup Manager, no Migrator.
I reported the issue yesterday and thus this [BUG] was created. Can only hope this is resolved as soon as possible with the highest urgency.
These bugs should really not happen with sufficient testing in the near future.
Hi, my destination server has a new installed Plesk 18.0.27 version and the source server has Plesk 18.0.26 , i received that error, is the same situation? So the issue is related to the extension Migrator and Plesk 18.0.27?
The new version brings a new 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 xxxxx.net -ignore-nonexistent-options failed with exit code 1:
stdout:
stderr: Unknown command: --restore-subscription
Any ideas?
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
Still not working.
"Failed to make APS applications dump. Not all applications data may be migrated.
Error message: Command execution failed on the local server with non-zero exit code"
"Failed to create the remote configuration dump on the target server. Not all settings may be migrated.
Error message: Command execution failed on the local server with non-zero exit code."
This used to work just fine.. can you please advise?
+1
Workaround 2 only works if the source is not already version 18.0.27.
A updated migration manager would be very much appreciated.
My issue seems to be resolved after updating to version 2.19.3
I'm getting the error while trying to migrate my sites from cPanel to Plesk. The current Plesk Migrator version is 2.19.2-916. Please solve the issue. Thanks.
After finally being able to downgrade the destination server and when I try to start the migration, this is what I get.
You guys did a great job pushing me into a corner where now I have to manually move each domain files and databases by hand.
+1. please, roll out a solution asap
Erik Blazynski you may click "follow" to subscribe for updates. Once fix is available article will be updated.
Alex Vojacek Please rest assured it is highest priority and fix will be delivered ASAP. If you can paste full error about database restore we may take a look.
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
So far so good, although I'm getting this error after several attempts.
Failed to perform an action on subscription 'a****r.com': Failed to transfer additional Apache/nginx directives Exception message: 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 agsdevserver.com -ignore-nonexistent-options failed with exit code 1: stdout: stderr: Unknown command: --restore-subscription
It seems migration is still going so it is not a fatal error.
Thank you for the quick action, Julian!
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.
It gives all kinds of errors. If I export from a normal backup and try to import from the CLI it imports the sites but tells me that all my databases are corrupted.
If I export from CLI on the origin server with your method and then ftp the file to the destination server and try to do an import, it throws this error after what appears to be a full import.
Unable to import file as dump: pmm-ras failed (Error code = 1): Transport error: 0 byes were read but 65304394 expected.
I suspect the problem appears to be coming from the backup process itself, not restore process.
This is so easy to replicate now:
Do a backup with:
plesk bin pleskbackup --domains-name mydomain.com --output-file="/root/example.com.zip" -v
Then try to check that newly created backup with:
plesk bin pleskrestore --check-backup "example.com.zip"
You'll see the same error show up:
Unable to import file as dump: pmm-ras failed (Error code = 1): Transport error: 0 byes were read but 65304394 expected.
So it seems the problem starts at the backup creation phase, that is the only explanation I can come up with for this sorts of errors. I've never had a single backup/restore or migration issue before.
My domain has 25GB of compressed data, so it seems like your basic backup/restore functionality is either not working at all or just breaks with big backups.
There is no way to do a backup/restore, not with your methods, not by manually inserting the backup files, there is just not a single method that works, period.
You need to issue an update that reverts to the 18.0.26 behavior ASAP and then concentrate on fixing it for good, because as it is, we have lost the migration backup/restore funcionality completely.
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,
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
@Malgorzata Modzelewska,
Sorry for the misunderstanding. The message "Unable to find archive metadata" is quite general, so I would advise checking the logs anyway. In case of backup/restore process they are: /var/log/plesk/PMM/ and /usr/local/psa/PMM/rsessions.
If you already have your HD mounted to the server you can simply transfer the backups to the DUMP_D directory (which is defined in /etc/psa/psa.conf for Linux or in the Windows registry "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PLESK\PSA Config\Config"). Backups lower than 2 GB can be uploaded via Plesk UI directly and restored after that.
Hello @Malgorzata Modzelewska,
Try to check if the Plesk Migrator is newer than v2.19.4. If it's newer, try to check the migration logs for more details:
/usr/local/psa/var/modules/panel-migrator/logs//usr/local/psa/var/modules/panel-migrator/sessions/Thank you for responding. How can I be notified when the fix is available?
Any prediction when this will be fixed? I'm migrating away a couple of VPS's from Str*to since they have serious performance issues, but now migrating is really a pain since I can't use the migrator.
Alex Vojacek please update your destination server to 18.0.27 and then migration from the old server. The bug has been fixed.
Can you guys disable the ability for people to upgrade until the bug is fixed? I think it will help reduce the amount of people that can get in trouble over this.
Thank you for this good work and fast work. Thank you very much!
Please sign in to leave a comment.