• 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.

Dump file of Plesk7.5.2 (FreeBSD) can not be restored on Plesk7.5.2 (RHEL3)

T

Tekkel

Guest
In Plesk7.1.x it was possible to backup on a server running FreeBSD and to restore that dump on a Plesk7.1.x server on RHEL.

Since Plesk7.5.x is around, it seems that the MySQL versions are to different. The dump made by the FreeBSD server puts things in the dump that cannot be understood by the MySQL server on the RHEL3 server:

The dump made by FreeBSD server looks like this:

Code:
CREATE TABLE `book` (
..........................
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

The part "ENGINE=MyISAM DEFAULT CHARSET=latin1;" is not understood by MySQL on RHEL3 server. When it is replaced in this form:

Code:
CREATE TABLE `book` (
..........................
) TYPE=MyISAM;

The MySQL version numbers are:
FreeBSD 4.9, Plesk7.5.2: MySQL mysql-4.1.7
RHEL3, Plesk7.5.2: MySQL 3.23.58-1

This is a solution for restoring one database, but not for a server with 100+ domains. Is there a way to let the FreeBSD make a dump that can be imported on the RHEL server?
 
OK, solved it myself.

There needs to be a line in /etc/my.cnf:

[mysqldump]
compatible=mysql323

When this line is added, the backup of the FreeBSD server makes dumps that can be read by mysql 3.23.x on the RHEL server.
 
Back
Top