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
37 comments
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?
This is not working again in 18.0.27 Same version on both servers.
Hi Erik Blazynski and Gianluca.
Yes, the issue occurs if on destination server you have 18.0.27, source version can be any.
Most suitable workaround at this moment is to do backup on source, upload it to destination to move data.
We working on permanent fix with high priority here and expect to issue it in a couple of days.
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 !!
Thank you for responding. How can I be notified when the fix is available?
+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.
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.
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.
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.
Hey!
Same problem here.
I wan't to migrate from 12.5.30 to 18.0.27...
I have to migrate 150 clients with websites ans email, so workaround 1 is no option!
Please fix the bug very soon!
Greetings!
The backup-restore suggestion is far from straight forward.
Needs appently a lot of manual confilict resolution. Like many others here, I would appreciate an ASAP solution - stuck in an emergency migration and doing it on site/file lovel now...
Thaks for fix ASAP. Regards.-
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.
+1
Workaround 2 only works if the source is not already version 18.0.27.
A updated migration manager would be very much appreciated.
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.
@Alex Vojacek @Markus Plänitz @Sander Scheer @Pete Murphy @Claus Siebeneicher @HMnet @Abdelrahman Moussa @Michel vd Lingen.
The bug has been fixed and the resolution has been added to the article. Please proceed by updating Plesk Migrator and let us know.
Alex Vojacek please update your destination server to 18.0.27 and then migration from the old server. The bug has been fixed.
Thank you for this good work and fast work. Thank you very much!
THANK YOU !!!
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.
My issue seems to be resolved after updating to version 2.19.3
Thank you for the quick action, Julian!
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.
It worked !. Aside from that minor issue my server is now migrated. Thank you so much !
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?
I moved data from Centos 7 to Ubuntu a couple of days ago (Plesk 18.0.26) and never got errors.
Updated to 18.0.27+Migrator tonight. Again moving data from Centos 7 to Ubuntu 18.04. Test run shows weird errors.
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?
@Alex Vojacek, @Alex, @gregtoffer,
Thanks for bringing this to our attention!
Here's the article about the issue: https://support.plesk.com/hc/en-us/articles/360013860439
The solution is the same: update Plesk Migrator to version v2.19.3
@...
I still have the 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 orcafusioncreativa.com -ignore-nonexistent-options failed with exit code 1:
stdout:
stderr: Unknown command: --restore-subscription
even though am in the latest version of the migrator
Please sign in to leave a comment.