• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

migration from one server 8.3 to another 8.3

A

arwed

Guest
Hi,
due to a hardware defect I need to move all my clients/domains/databases to a new server.
Both have Plesk 8.3.0 with identical my.cnf files.
1. If I migrate a client with a database, the data is allways converted to from utf-8 to latin1 in the new utf-8/utf8_unicode_ci database.

2. In certian directories we had to modify the rights (e.g chown wwwrun.www chmod 775)
After migration the rights have to be changed manually again.

Isn't there a way to do a 100% 1:1 migration without any changes in the database an rights?
Regards
Arwed
 
Hello

Plesk migration manager switches the database encoding by default and generally there is nothing to do with it. Either youl have to manually change the encoding after migration, or dump the databases
manually on the source server and then restore them on the new one with mysqldump, for example:
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` --all-databases --skip-set-charset > all_db_dump.sql

The problem with the permissions is related most probably to some custom applications installed not through Plesk CP but some other way. Generally all the files in the domain's document root are owned by the domain ftp user and the group psacln. It is made by design and no wonder the migration
manager overwrites the permission to satisfy the requirements. In this case there is also nothing to do with it, it is the way the Plesk migration manager works.
 
Back
Top