Important Plesk Migrator extension

[eug]

We have released the new version of Plesk Migrator extension - v2.1.8

Changelog:

[+] Mail content can now be migrated from hMailServer 5.
[+] Plesk Migrator can now be installed from Plesk Extensions Catalog on Linux.
[-] In some cases, restoration of Microsoft SQL database or MySQL database on Windows failed with an error on access to the dump. (PMT-3187)
[-] Secondary transfer of a mail message without header to SmarterMail failed. (PMT-3189)
[-] When a subscription was migrated from Plesk Expand with Centralized Mail server, mail service was disabled on the target server. (PMT-3148)
[-] The Overview tab of the Plesk Migrator user interface had bad appearance when some particular Plesk skins were used. (PMT-3201)
[-] Sites having errors on both source and target servers were marked as migrated with errors during the post-migration check.(PMT-3172)
[-] An add-on domain could not be migrated if a DNS record corresponding to its name already existed in the target server's DNS template. (PMT-2580)

 

[Antrax1]

Hi,

I have this error migrating from plesk 12.5 to plesk 17:

Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Command execution failed on the local server with non-zero exit code.
command: rsync -l --chmod=Fu=r,Du=rwx,go= -e 'ssh -i /usr/local/psa/var/modules/panel-migrator/sessions/20161101090640/ssh-keys/id_rsa.XXX.XXX.XXX.XXX -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/var/modules/panel-migrator/sessions/20161101090640/ssh_upload.1 [email protected]:/tmp/version
exit code: 255
stdout:
stderr: Permission denied (password).
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1]

That is a critical error, migration was stopped.

IP was changed to XXX.XXX.XXX.XXX

I see this solution https://kb.plesk.com/en/129028 but the solution is install the latest MU, I have the last version.

 

[SunRabbit]

Hi,
I have this error migrating from plesk 12.5 to plesk 17:

stderr: Permission denied (password).

The two possible reasons from the top of my head:
1) You are trying to migrate using non-root but some other user account;
2) Key authentication is disabled in the sshd configuration (otherwise you should get "stderr: Permission denied (publickey,password)" error).

 

[eug]

Plesk Migrator 2.2.2 released!

What's new:
[+] [Plesk Onyx only] Migration to Plesk Multi Server is now supported.
[+] Mail migration from hMailServer 5 is now supported.
[*] During migration from cPanel, it is now possible to change document root of a subscription.
[*] Migration of mail messages using the IMAP protocol from any custom server is now possible.
[-] After migration using the IMAP protocol, all messages on the source server were marked as read. (PMT-2939)
[-] It was impossible to migrate several aliases of the same mail account. (PMT-3190)
[-] In some cases, migration from Plesk Onyx failed and a confusing error message was displayed. (PMT-3175)
[-] Post-migration checks did not start automatically after migration. (PMT-3160)
[-] It was impossible to enable automatic deployment of RPC agent after an attempt to start migration with manual deployement of RPC agent. (PMT-3229)
[-] Post-migration checks log file contained error messages related to non-existent subscriptions. (PMT-2861)

#### Linux
[-] In some cases, migration from Plesk failed if TLSv1.0 was disabled on the target server. (PMT-3276)
[-] Migration failed if there were no 'apache' user on the source server. (PMT-3213)
[-] If the Plesk Migrator extension installation failed, no error messages were displayed in the Plesk user interface. (PMT-3204)

#### Windows
[-] A subscription with a DotNetNuke application failed to migrate from one Plesk Onyx server to another. (PMT-3192)
[-] An incorrect message was displayed during migration of a subscription using a database with several tables. (PMT-3198

Please update here if there are any questions or suggestions.

 

[eug]

We are glad to announce release of Plesk Migrator 2.3.2

What's new:

[+] A new mode was added to migration from Confixx so that mail users will be able to log in to their mail accounts on the target server with their original usernames and passwords.
[+] During migration from cPanel, it is now possible to change the document root of a migrated domain.
[+] It is now possible to migrate mail content to/from Plesk Onyx using a remote SmarterMail server.
[-] Domain alias could not be migrated if its name was present in the DNS template. (PMT-3340)
[-] During migration, long FTP user names (with 16 or more symbols) were truncated to 15 symbols. Now the maximum length for FTP names is 16 symbols that corresponds to the limitation of Plesk. (PMT-3320)
[-] An error occured during adjusting application files after migration if the file names contained non-ASCII symbols. (PMT-3334)
[-] The description of copy content options in Plesk Migrator user interface was insufficient. (PMT-3330)
[-] Migration of user accounts associated with subscription was performed incorrectly. As a result, the corresponding subscription could fail to migrate. (PMT-3351)

#### Linux

[-] Web content could not be migrated from cPanel, Confixx, or Parallels Pro Control Panel for Linux, if CageFS was enabled on the source or target server. (PMT-3333)
[-] Mail users having the permission to log in to Plesk on the source server could not log in to Plesk on the target server after migration. (PMT-3354)

#### Windows

[-] Mail flags and folders were lost during migration from hMailServer 3. (PMT-2943)
[-] Migration to/from Plesk failed if the Plesk database had a name other than 'psa'. (PMT-3329)

Your feedback is appreciated.

 

[fmu83]

Hi,

it seems that there is a bug in this feature:

[+] A new mode was added to migration from Confixx so that mail users will be able to log in to their mail accounts on the target server with their original usernames and passwords.

- Server Configuration:

Source Server: Debian / Confixx 3.3.9

Target Server:
Ubuntu Server 16.04.01 LTS
Plesk Onyx v17.0.17_build1700161028.14 os_Ubuntu 16.04
Plesk Migrator 2.3.2
Dovecot IMAP/ POP3

During migration from Confixx the mbox is identified corretly from the Plesk Migrator Script
2017-01-05 12:58:05 DEBUG Defined a Confixx POP3 mbox for this email: 'web41p1'

Result:
- SMTP Auth ist working with User web41p1
- IMAP / POP3 is not working

Can you have a look on it? This feature is citical for us to migrate old confixx accounts without doing changes at the customer side.


Thanks & BR

 

[eug]

Hi,

it seems that there is a bug in this feature:

[+] A new mode was added to migration from Confixx so that mail users will be able to log in to their mail accounts on the target server with their original usernames and passwords.

- Server Configuration:

Source Server: Debian / Confixx 3.3.9

Target Server:
Ubuntu Server 16.04.01 LTS
Plesk Onyx v17.0.17_build1700161028.14 os_Ubuntu 16.04
Plesk Migrator 2.3.2
Dovecot IMAP/ POP3

During migration from Confixx the mbox is identified corretly from the Plesk Migrator Script
2017-01-05 12:58:05 DEBUG Defined a Confixx POP3 mbox for this email: 'web41p1'

Result:
- SMTP Auth ist working with User web41p1
- IMAP / POP3 is not working

Can you have a look on it? This feature is citical for us to migrate old confixx accounts without doing changes at the customer side.


Thanks & BR

Hi,

We need to take a look. Please file ticket with Migration Team at https://www.plesk.com/professional-services/free-migration/ . Be ready to provide access to source and destination servers.

 

[eug]

Plesk Migrator 2.4 released!

What's new:

• During migration of mail content from a custom panel, it is now possible to define configuration settings like for a subscription content. In particular, it is possible to specify files or directories that should be excluded from copying or to define advanced file mapping.
• A subscription belonging to a reseller could not be synchronized with an add-on service plan after migration. (PMT-3413)
• Post-migration checks did not detect error messages or warnings on a web page in case when the HTTP code and the title of the web page were identical on the source server and on the target server. (PMT-3388)
• During migration from a custom panel, post-migration checks were run for an enabled subscription with disabled main domain. As a result, error messages were reported. Now no post-migration checks are run in this case. (PMT-3378)
• During migration from a custom panel, post-migration checks failed if a subscription had an add-on domain with an IP address other than the subscription’s IP address. (PMT-3371)
• Post-migration checks did not detect some typical PHP error messages or warnings on web pages. (PMT-3389)

#### Linux

• Migration could not be started on CentOs 5. (PMT-3417)
• An unclear error message was displayed during migration if the configuration files of migrated applications contained non-unicode symbols. As a result, the adjusting of all other applications of the migrated subscription failed. (PMT-3398)
• An unclear error message was displayed during migration if WordPress configuration files contained non-UTF-8 symbols. As a result, the adjusting of a particular WordPress instance failed. (PMT-3400)

#### Windows

• Plesk Migrator can now be configured to detect the scriptiong settings (PHP version, ASP.NET version, ASP) of a subscription on the source server and migrate them properly.
• Migration from a custom panel failed if the hosting description contained binary data in password fields of hosting description. (PMT-3390)
• If the web.config file of a web site contained XML namespaces, the web site could stop functioning after migration. (PMT-3387)
• Migration could fail if many (more than 10000) application files were changed during adjusting. (PMT-3409)
• After migration from a custom panel there were no write permissions in the document root of a migrated subscription, it these permissions were not set explicitly in the hosting description. Due to this issue, the permissions settings sometimes were lost during migration from Plesk Onyx to Plesk Onyx. (PMT-3407)
• Web Presence Builder was not registered in Plesk after migration to Plesk for Windows 12.5 or Onyx. (PMT-3369)
• Some errors related to Microsoft SQL Server were not reported in Plesk Migrator log. (PMT-3362)
• If migration of a Microsoft SQL Server database failed, Plesk Migrator added a database dump to an existing dump file during each new attempt to migrate, thus increasing the size of the dump file. (PMT-3411)

 

[eug]

Plesk Migrator Update 2.5

What's new:

• Migration from DirectAdmin 1.51 is now supported.
• Migrated databases are automatically renamed before restoration to avoid conflicts in cases of the same names of databases and database users.
• Administrator can now configure the depth of checked web site links in post-migration checks.
• Migration from Plesk 11.0 failed when a custom button with an icon in PNG format was configured on the source server. (PMT-3458)
• Migration on Windows could not start if the path to the ‘plesk’ utility was not specified in the PATH variable of the target server. (PMT-3452)
• Migration on Windows could not start if no PHP handlers were installed on the target server. (PMT-3472)
• MySQL databases could not be migrated if an incorrect or empty password was set in the MySQL configuration file. (PMT-3394)
• Adjusting application settings could work infinitely in case when the parent folder of a web site on the source server contained symbolic links. (PMT-3412)
• If an additional domain’s IP address differed from the subscription’s IP address, the DNS records of the additional domain could not be migrated. (PMT-3445)

 

[eug]

Plesk Migrator Update 2.6

What's new:

• Migration of files, databases, and WordPress sites from any server available via FTP is now supported.
• Database content could not be synchronized in Plesk for Windows when different remote Microsoft SQL servers were used by the source and the target servers. (PMT-3509)
• A database was duplicated during second migration of a subscription having capital characters in name. (PMT-3535)
• DirectAdmin: content of administrator’s subscription became unavailable if the owner of the document root folder was incorrect. (PMT-3508)
• DirectAdmin: migration could not be started if a customer with non-unicode symbols in the name was present on the source server. (PMT-3540)
• DirectAdmin: migration could not be started if a mail auto-reply had been created for a domain on the source server and then the file with the auto-reply message had been deleted. (PMT-3542)
• DirectAdmin: migration was blocked if a cron task on the source server could not be parsed. (PMT-3544)
• After migration from a custom panel, the Apache error log file could not be opened in the Log Browser because of incorrect permissions. (PMT-3460)
• MySQL server databases could not be migrated from DirectAdmin if a remote MySQL server was used on the source server. (PMT-3545)

 

[eug]

Plesk Migrator 2.6.11 released

This is bugfix release for Site Migration feature announced in version 2.6

• Migration of folders from a web site failed if an FTP server on the source server returned relative paths in the list of the folders. (MT-3563)
• The list of folders for migration could not be obtained by Plesk Migrator if “.” or “..” were present in the folders list returned by the FTP server. (PMT-3569)
• Migration of a web site content failed if the FTP connection was unexpectedly closed on copying the content. (PMT-3567)
• Migration of a web site content failed after upgrading Plesk Migrator from version 2.1 or earlier to a later version. (PMT-3568)
• The database of an imported WordPress site could not be migrated if the time of files migration exceeded the IDLE timeout of the source FTP server. (PMT-3575)
• A WordPress site could not be migrated if redirection was enabled on the source domain. (PMT-3571)
• Website migration could be blocked if the session folder was deleted after the migration. (PMT-3576)
• Website migration failed with an uninformative error message if the document root could not be detected automatically. (PMT-3574)
• The migration progress dialog got stuck if an error occurred while retrieving data from the source server. (PMT-3573)

 

[trialotto]

@eug,

A couple of remarks or questions to function as feedback:

- migration of individual domains is not or does not seem to be possible: this would be rather important when hosting site mirrors on another server, (and)
- no explicit button to get on the start page: quite handy when running multiple (unfinished) migrations and/or when wanting to do some re-syncing
- migration of percona to mysql databases will not work properly in exceptional cases (not a real issue, this is minor)

I noticed that the Plesk Migrator does not always get updated directly, when a new version has been released.

The latter is propably not related to the Plesk Migrator extension, but more or less related to "extension management".

Can someone have a look at that?

Regards......

 

[eug]

@trialotto

- migration of individual domains is not or does not seem to be possible: this would be rather important when hosting site mirrors on another server, (and)

The feature is implemented explicitly for migration of website (its content + DB) into an individual domain in Plesk. Here is documentation Web Site Migration . Please clarify what exactly is not possible or does not seem to be so.

The scenario of site content synchronization is covered for WPT 2.0 site yet. Thank you for the suggestion, we will think to enable this for any site (for example, as CLI command that can be added as a cronjob) in further Migrator versions.

- no explicit button to get on the start page: quite handy when running multiple (unfinished) migrations and/or when wanting to do some re-syncing

If we are talking about site [content] import, the process is always individual for each pair of src_site:dst_domain_in_Plesk as there is required to enter (at least) ftp credentials of source site which are supposedly different for different source sites.

In further release we will make the process easier for admin - there will be a button inside Plesk Migrator on the same level with "Start a new migration" that will allow admin to choose inside which domain one would like to perform the migration of external site content & DB and then it will lead to the 1st screen of site import inside this domain.

- migration of percona to mysql databases will not work properly in exceptional cases (not a real issue, this is minor)

Please describe in more details in which exceptional cases this does not work with Percona?

I noticed that the Plesk Migrator does not always get updated directly, when a new version has been released.

Extensions are automatically updated to the latest version once a three day. You can check for which extensions there are available updates in Extensions -> Settings -> "Check for updates".

 

[trialotto]

@eug,

I will respond to your post via a PM, as soon as I have some time left.

By the way, did you state that extensions are updated once per three days??

Regards....

 

[jangali]

Good day,
Moved the site to another hosting. At first I decided to try to transfer using Website Importing in the Plesk panel of the site, but then transferred the site manually via FTP.
Can you please tell me, how to stop the process in the Control Panel - Website importing, and it's spinning - Info: Website content import is in progress.

 

[eug]

Hi Jangali,

Please tell why you decided to stop website import by Plesk and decided to perform it manually?

For now, there is no such function as site import cancellation. This feature will be added in further releases.

 

[jangali]

Hi. eug,
I decided to move the site manually, because in fact a few hours nothing happened.
Now it will spin - Import procedure?
How does that affect the site?

 

[eug]

Hi jangali,

If there is endless migration operation for too long time, that means the process in backend has died. Just does not mention it keeps spinning on the screen.

We know about such bug with site import stuck, it is recorded as PMT-3599. In nearest Plesk migrator release planned on this week, there will be included fix for the bug. Then you (Plesk admin) will need to apply migrator update and you will need to re-run site import for this domain on the screen that you showed above. When it is completed with no error, it will show "green" status on the screen.

Also, in nearest Plesk Migrator updates we will improve error reporting for site import so that there is visibility on what is going on. Please check for updates.

 

[eug]

Plesk Migrator 2.7

What's new:

• When migrating to a Plesk server using a non-English locale, a confusing error message was displayed if the name of one or more files or directories on the source server contained national characters. (PMT-3294)
• The lack of notifications or a progress bar during post-migration checks could confuse the user. (PMT-3309)
• Migration could fail if multiple perl versions were installed on the source server and the PATH environment variable pointed to a custom perl version. (PMT-3376)
• Web content was not copied if SSH access to the source server was limited to specific users and the users ‘plesk-migrator*’ were not allowed access. (PMT-3385)
• PostgreSQL databases could not be migrated if PostgreSQL server version 9.5 or later was installed on the source server. (PMT-3391)
• Under specific circumstances, the “Failed to remove temporary user” error was displayed during migration even if the temporary user was removed. (PMT-3399)
• Entries in the subscription log were not sorted by date. (PMT-3525)
• Microsoft SQL Server databases could not be migrated if the Microsoft SQL Server instance on the source server was configured to use a nonstandard port. (PMT-3547)
• The header on the migration screen was corrupted if the Plesk interface language was set to Italian. (PMT-3548)
• When migrating from DirectAdmin, quota for mailboxes was set to 100 MB even if it was set to unlimited on the source server. (PMT-3550)
• Trying to re-sync business objects after deleting a mail account on the source server produced a confusing error message. (PMT-3552)
• During site migration, WordPress sites using a remote database were not re-configured to use the database migrated to the destination server’s MySQL server. (PMT-3562)
• Removing the session folder created after initiating a site migration resulted in empty session folder and configuration file getting created. (PMT-3579)
• If during migration names of some databases and database users were changed, after upgrading Plesk Migrator to the latest version and restarting the migration, the name changes were not preserved. (PMT-3582)
• When migrating from DirectAdmin, if a mailbox and a forwarder with the same name were present on the source server, only the forwarder was migrated. (PMT-3585)
• When migrating from Plesk Onyx, extension files stored in the “/usr/local/psa/var/modules/” directory were assigned incorrect ownership. (PMT-3587)
• Migration from DirectAdmin failed if a DNS zone contained a white space character as a separator. (PMT-3600)
• When migrating from Plesk, the “Restrict the ability to follow symbolic links” hosting plan setting was disabled on destination server even if it was enabled on the source. (PMT-3602)
• Migration from DirectAdmin failed if a protected directory created in DirectAdmin was not physically present on the file system. (PMT-3618)
• Migration from DirectAdmin failed if one or more mail users on the source server did not have a home directory configured. (PMT-3645)
• Migration to Plesk Onyx could fail if one or more customers on the source server had unicode characters in their name. (PMT-3646)

 

[mr-wolf]

ToDo

• When migrating from Courier to Dovecot, the IMAP-subscriptions are not migrated. These should be placed in the file /var/qmail/mailnames/*/*/Maildir/subscriptions, but they are NOT

It could be as easy as

sed '/^INBOX$/d;s/^INBOX//g' courierimapsubscribed >subscriptions