Plesk Migration doesn't copy mysql database

[f.reddy]

Hi there,

I try to migrate some domains from a heavily used server to a new one.
Both are on Version 11.0.9. Everything seems to work fine but the mysql database is emtpy (user an database are present).
The logs tell me, the database gets pulled via scp from the source but I can't find any information about the database processing.
It works very fast, so wasn't able to check the database file on the source. It gets deleted immediately after the transfer.

Can someone tell me, where the database import is logged?

Thanks in advance

 

[IgorG]

It is really strange. I can suggest you try to use Plesk Mass Migration Script http://forum.parallels.com/showthread.php?t=257075 or this article for migration troubleshooting - http://kb.parallels.com/en/9679

 

[f.reddy]

Hi Igor,

the Mass Migration Script failes because the destination server has only one IP address. (IP mapping fails).
I tried to get a snapshot of the database file while the transfer is running. So I hit ls -lh on the source again and again.
After some tries I got it. The database backup on the source server has only 437 bytes. Seems to be empty.
Is there a possiblity to debug the database dump process?

Thanks!

edit: Some news:

I just migrated another domain successfully.
Also I was able to have a look into the db dump of the failing domain.

-- MySQL dump 10.11
--
-- Host: localhost Database: main-newsletter
-- ------------------------------------------------------
-- Server version 5.0.95

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

Thats only the "header"... the tables are missing...

 

[paulieG]

Hi,

How big is the database you're trying to migrate?
What happens if you attempt a Plesk backup of the domain? Does that give you a more useful error?
What about a msyqldump from the command line of the specific database?

The only problem that comes close to this that I've seen is when a Plesk backup can't be performed as mysqldump attempts to dump the entire contents of a database table in one statement which exceeds the max allowed packet size. Hence my queries about the outcome of a Plesk backup and a mysqldump.

If it is this then we fixed it by adding the following to /etc/my.cnf :

[mysqldump]
max_allowed_packet 128M

Hope this helps,

Paul.