Facebook
Twitter
Pete Murphy
New Pleskian
Hello, after the last update to obsidian 18.0.27 I have problems with migrations with Plesk Migrator. I can't do them. Any ideas? Thank you
-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations. -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
Resolved PROBLEM WITH PLESK MIGRATOR AFTER UPDATE TO OBSIDIAN 18.0.27
- Thread starter Pete Murphy
- Start date
If you are getting an error like:
Then we are aware of it and investigating it already.
If you get any other error please provide more information like: OS and Plesk version on both servers, exact errors, etc
Code:
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).Then we are aware of it and investigating it already.
If you get any other error please provide more information like: OS and Plesk version on both servers, exact errors, etc
Pete Murphy
New Pleskian
Yes. It is that same problem. Both versions of plesk, Source Panel as Target Panel, have the same version, the same OS, and all settings are the same. Thanks for the reply. I hope it will be resolved soon so I can finish my work.-
This is being checked under the bug ID PMT-4781
Pete Murphy
New Pleskian
So? You mean, maybe with a new update, will it have a solution? Thanks again
[BUG] 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 there are now also w/a available in the article
HoracioS
Regular Pleskian
Same problem here !!! Including with Extension Site Import and Mail Import...
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.
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.
> Same problem here !!! Including with Extension Site Import and Mail Import...
It's weird because the Site Import does not use the functionality of backup/restore system. Could you please clarify where you get this error message? So screenshots or screencasts could also be very useful.
It's weird because the Site Import does not use the functionality of backup/restore system. Could you please clarify where you get this error message? So screenshots or screencasts could also be very useful.
I am glad to announce that yesterday we have published Plesk Migrator v2.19.3 (Plesk Migrator - Plesk Extensions). It completely solves the underlying issue.
