Symptoms
- An object (Database, Database user, Subscription etc...) is not migrated even if selected
- No errors are shown for the specific object
-
In the debug.log from the migration session, the following can be found:
=|2023-02-24_13:10:42,410|D|ST1|core.safe|example.com||MigrationNoRepeatError: Failed to find imported dump XML file for subscription. Most probable reason is that dump file is not valid or corrupted. To investigate the issue it is recommended to check debug log for errors happened during "pmmcli --import-file-as-dump" operation.
or
|2023-02-27_13:36:37,491|D|ST1|core.actions.deploy.panel_users_utils|example.com||Auxiliary user '[email protected]' for ''example'' already exist, so skip it
=|2023-02-27_13:38:46,906|D|MT|core.runners.base|||Line 254 error: Element 'mailuser', attribute 'deployer-action': The attribute 'deployer-action' is not allowed.
Cause
Plesk Migrator extension bug with ID PMT-4938
Resolution
As a workaround, and to maintain the consistency of the data transfer:
- Create a full server backup on the source
- Transfer the backup to the target
- Restore the backup on the target server
with