• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problems with Plesk Migration Manager

G

greyboy

Guest
Hello,

We are trying to move many sites from a cPanel server to a Plesk v7.5.4_build75051209.14 os_RedHat el4 machine and are experiencing many problems.

The process goes like this.

1) I package up the sites using cPanel9.pl --no-compress --accounts=acctname
2) SCP the files over to the new server
3) copy and chown the files to /usr/local/psa/PMM/archives
4) copy the cPanel.xml file to /usr/local/psa/PMM/var/dump.xml
5) Proceed to use the PMM took from within Plesk.

However, we are seeing quite a few errors. Most seem to be OK anyway, but the database errors are not. This is common for almost every domain:

1. Failed deployment of database user username of database username_dbname
Execution of '/usr/local/psa/bin/database.sh' '--update' 'username_dbname' '-add_user' 'username' '-type' 'mysql' '-passwd' '' failed with the return code 1.
STDOUT:

STDERR:
Unable add user to database: Unable to create the database user: User username already exists.

[Plus many more...]

I believe the problem is that username is already assigned to another database, which is common. A single username can span multiple databases, so this script fails.

I see how to manually manipulate the psa database to account for this, but it's a tedious process.

Does anyone here have any experience they can share regarding this?

Thanks,
-N
 
Back
Top