Knowledge Base

Plesk Migration fails with max_allowed_packet parameter warning: Could not backup database

Symptoms

Migration fails with error:

PLESK_ERROR: Could not backup database ‘wordpress_f’ of type mysql[Method not found: ‘Int64 psarepository.Repository.Pack(System.String, System.String[], System.String[], System.String, System.String, System.String, Int32, Int64, System.Collections.ArrayList, System.Collections.ArrayList)’.]

PLESK_WARN: domain “example.com” server.
The ‘max_allowed_packet’ parameter on the source database server is 16777216, which is bigger than on the destination server, where it is 1048576. Some database objects for the domains specified below might not be restored. Please increase the ‘max_allowed_packet’ value on the destination database server. 1 domain(s) will be affected.

Cause

Low max_allowed_packet value is set for the destination MySQL server.

Resolution

Click on a section to expand

Plesk for Linux

Connect to the server via SSH
Check max_allowed_packet parameter values on both source and destination servers in /etc/my.cnf file.
Set the value greater than it is set on the source MySQL server:

# cat /etc/my.cnf | grep ‘max_allowed_packet’
max_allowed_packet=96M
Restart MySQL server:

# service mysql restart

Note: service name might vary depending on the OS, it might be mariadb or mysqld
Restart the migration

Plesk for Windows

Connect to the server via RDP
Check max_allowed_packet parameter values on both source and destination servers under "%plesk_dir%"DatabasesMySQLdatamy.ini path.
Set the value greater than it is set on the source MySQL server:

C:> “%plesk_dir%”DatabasesMySQLdatamy.ini | findstr max_allowed_packet
max_allowed_packet=96M
Restart MySQL server going to Plesk Service Monitor > SQL Server > Restart
Restart the migration