• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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