• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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 problem 8.2 to 8.6

G

GabrielGonzalez

Guest
Hello,
I did a backup on a Plesk 8.2 and restored it on another server with Plesk 8.6 installed.
The problem is that now the database is corrupt and many columns are missing (since server is expecting a database with 8.6 format).
One error I get is "Unknown column 'traffic_bandwidth' in 'field list'" ("hosting" table) or "Unknown column 'guid' in 'field list'" ("domains" table)

What can I do to fix Plesk 8.6 server?

Thank you
 
Hello,

I'd change the version parameters of the plesk server and force upgrade the plesk to 8.6. That may help.
 
Solved

Hello,
I solved this updating the old server to 8.6 and then generating backup again and restoring it in the server which already had 8.6 installed. Then backup whole database and restore it in the new server to make every table compatible again.

Thanks anyway!!
 
Back
Top