• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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