• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Migration from Plesk 10 -> 12 Mysql Issues.

nuegozu

New Pleskian
I performed a migration from Plesk 10 -> 12 using the Migration & Transfer Manager. When complete I received a warning that 'Errors occurred during deployment of database content', namely a Mysql 1054 error 'Unknown column' for a particular database.

Although the migration completed and it appears that all the website data etc was transferred correctly there are several databases missing on the destination server so I am wondering if the error above caused the database transfer process to die.

I understand that the database that caused the error has now been fixed but my question is how to re-transfer the missing Mysql data. Can I just 'Start New Migration' from 'Migration & Transfer Manager' or is there another proceedure I have to follow? e.g. is it possible to transfer just the databases from the command line?
 
After further investigation I believe the problem was actually caused by the devs creating databases manually outside of Plesk. As there was no record of these databases in the Plesk config files this is probably the reason that they weren't transferred during the migration.
 
Back
Top