Migration from 10 to 12.5 failing

[Kevin Clawson]

I am getting this error in the logs:

=|2015-11-04_21:05:23,857|D|MT|parallels||| raise MigrationError(full_failure_message)
=|2015-11-04_21:05:23,857|D|MT|parallels|||MigrationError: Failed to import backup dumps to target panel's repository
=|2015-11-04_21:05:23,857|D|MT|parallels|||Cause: Failed to import backup XML: errcode must be '0' (no errors) or '116' (backup sign error).
=|2015-11-04_21:05:23,857|D|MT|parallels|||Output of pmmcli utility:
=|2015-11-04_21:05:23,857|D|MT|parallels|||<?xml version="1.0" encoding="UTF-8"?>
=|2015-11-04_21:05:23,857|D|MT|parallels|||<response>
=|2015-11-04_21:05:23,857|D|MT|parallels||| <errcode>152</errcode>
=|2015-11-04_21:05:23,857|D|MT|parallels||| <errmsg>Unable to import file as dump: The file you are trying to upload is not a valid backup file</errmsg>
=|2015-11-04_21:05:23,857|D|MT|parallels|||</response>
=|2015-11-04_21:05:23,857|D|MT|parallels|||
=|2015-11-04_21:05:23,857|D|MT|parallels|||That is a critical error, migration was stopped.
+|2015-11-04_21:05:23,874|E|MT|parallels|||Failed to import backup dumps to target panel's repository
=|2015-11-04_21:05:23,874|E|MT|parallels|||Cause: Failed to import backup XML: errcode must be '0' (no errors) or '116' (backup sign error).
=|2015-11-04_21:05:23,874|E|MT|parallels|||Output of pmmcli utility:
=|2015-11-04_21:05:23,874|E|MT|parallels|||<?xml version="1.0" encoding="UTF-8"?>
=|2015-11-04_21:05:23,874|E|MT|parallels|||<response>
=|2015-11-04_21:05:23,874|E|MT|parallels||| <errcode>152</errcode>
=|2015-11-04_21:05:23,874|E|MT|parallels||| <errmsg>Unable to import file as dump: The file you are trying to upload is not a valid backup file</errmsg>
=|2015-11-04_21:05:23,874|E|MT|parallels|||</response>
=|2015-11-04_21:05:23,874|E|MT|parallels|||

It looks like the backup being created in 10 is not translating to 12.5 for some reason. But when I migrated from 9.2 to the same 12.5 server, I don't get any errors. Any ideas?

 

[Alexey Baturin]

There are several such issues fixed in the latest 1.3.17 version of migrator. Could you please check which version of migrator do you have, and if it is not 1.3.17 then upgrade it to the latest one?
If upgrade won't help, we will need backup dump file to investigate.

 

[Kevin Clawson]

I am already on 1.3.17. Where do i find the right info for the dumps?

 

[Alexey Baturin]

First, let's try to find information about imported backup:
Open command line and type there command:
dir /s /b "%plesk_dir%\Backup\*WRONG*"
this should list files that could help us to figure out the issue. Put contents of them here.

 

[Kevin Clawson]

Get "File Not Found"

 

[Alexey Baturin]

Unfortunately, no useful information (
Let's go further. The dump is located here:
%plesk_dir%var\modules\panel-migrator\sessions\<session-dir-id>\plesk.backup.<source-id>.converted.zip

You could:
1) Try to validate the dump yourself according to http://kb.odin.com/en/117208. The instruction is quite complex, so if you don't want to spend your time on it, then:
2) Send it to http://talk.plesk.com/members/aleksey-filatev.174043/ from Odin team with a private conversaion (click link, then "Information" tab, then "Start a Conversation"). We will check it in ~12-14 hours and let you know the results.

 

[Kevin Clawson]

This is what I get:

c:\Users\FritzZwicky\Desktop\plesk.backup.source.converted>c:\xmllint\xmllint.exe --noout --schema "%plesk_dir%\PMM\plesk.xsd" migra_info_1511051604_formatted.xml
migra_info_1511051604_formatted.xml:

14: element client: Schemas validity error : Element 'client': This element is not expected. Expected is ( client-info ).migra_info_1511051604_formatted.xml fails to validate
​

If I am reading that right, that field should be changed from "client" to "client-info" Does that sound right? And is there a way to change it on the 10 server?

 

[Alexey Baturin]

Unfortunately no, no result again. Some details - we checked Plesk 10.x dump with Plesk 12.5 schema, and that is not correct.
One more thing to try is to import dump file as backup with backup manager in Tools & Settings. There you should disable signature check and disable password protection.
If it reports error, let us know.

Anyway we will look for a way to identify the root cause tomorrow, if you want to speed up the process you could send the dump file as I suggested before.

 

[Kevin Clawson]

Ok, thanks! Sent along that conversation and dump file

 

[Alexey Baturin]

We investigated the dump: according to files modification time, it seems that the dump was cached from the previous version of Plesk Migrator with the bug.

Try to start a completely new migration session (with "Start New Migration" button), or remove all dump files from %plesk_dir%var\modules\panel-migrator\sessions\<session-dir-id>\*.converted.zip and %plesk_dir%var\modules\panel-migrator\sessions\<session-dir-id>\*.raw.zip.