SYMPTOMS
I wish to migrate data from one of my servers to Plesk. What action should be done on the destination side in order to avoid errors during migration.RESOLUTION
1. All Plesk components that you wish to use have to be installed on the destination server. For example if the source server has Postgres or Mailman, these packages must be on the destination server, otherwise these components' data will not be migrated and you get the list of errors after migration is completed.2. Plesk license on the destination server also must meet all requirements that exist on the source server.
3. Enable "Server->Mail-> Only use of full POP3/IMAP mail accounts names is allowed" to avoid the problem that is described in the article 1211.
4. Configure Mailman on the Server->Set Up Mailman, otherwise mailing lists will not be created during migration.
5. Check that there is enough free disk space to make dump on the source server. It should be the same amount as data size you wish to migrate.
Destination server must contain free disk space at least twice the size of the data being migrated. It is needed to store the dump on the destination server and extract data from it.
6. Make sure that the default MySQL character set is 'latin1'. This encoding is used by Mysql by default, however if it was redefined in /etc/my.cnf, it is better to switch it back to avoid the problems with database restoration.
Current default characters set can be found with:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e 'status' | grep characterset
Server characterset: latin1
Db characterset: latin1
Client characterset: latin1
Conn. characterset: latin1