• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Migration of Big Account

S

sbenammour

Guest
I'm having a problem when I migrates one domain, it has a big MySQL database (2 GB). The migration starts correctly but after a while the connection is lost

How can I fix that?

Thank you
 
Hi

Probably the connection is lost by the timeout, you should check whether the ssh on the both servers is configured without timeout (ConnectTimeout value in /etc/ssh/ssh_config).
Examine /var/log/messages on the source server, migration logs (search in /usr/local/psa/PMM/ directory).
It is always possible to migrate manually, see here how to do it:
http://kb.swsoft.com/en/1152
 
Use Mysqldump

Use the mysqldump utility, to dump the database to file. Then tar/gz and transfer it with scp as described above.

A nice trick to prevent timeouts importing big database use mysql on shell again, like this:

"newdb" is your new, empty database wich will be the big one.
"big_db.sql" is the old, transferred from the other server:

/usr/bin/mysql -u admin -p`cat /etc/psa/.psa.shadow` newdb

Then execute your dump:

mysql> \. big_db.sql

Should take some time, but this worked with the biggest database i have, as every command is executed one by one.
 
Back
Top