Plesk Migration tools required-Urgent!

[Law]

Hi All,

We have a few legacy server which running on Plesk control panel. We have purchase new license key with new version of Plesk 12+, now are stuck with issues with migration tools for Plesk. Is there anybody can share the URL where/how we can retrieve those old migration tools?

We need version for Plesk 7.5, 7.6 and 8.6 for both window & linux platform.

Appreciate for your assistance!

Thank You!

Best Regards,
Law

 

[IgorG]

What do you mean "old migration tools"?
Also please read carefully requirements in Migration Guide - http://docs.plesk.com/en-US/12.5/migration-guide/introduction.75496/
As you can see, migration from very old version 7.x is not supported.

 

[Law]

Hi Igor,
Thanks for sharing! Our legacy server was Windows 2003 with Plesk 7.6, the migration agent and tools was required so we can migrate the domains to Plesk 8.6.
We are able to perform this from our legacy server in Linux platform. Meanning we are able to migrate domains from Linux plesk 7.6 to 8.6 and there after to plesk 12.0.

Hope you are able to advise us,

Thank You!

Best Regards,
Law

 

[IgorG]

Our legacy server was Windows 2003 with Plesk 7.6, the migration agent and tools was required so we can migrate the domains to Plesk 8.6.

What about just upgrade from 7.6 to 8.6 or 9.x?

 

[Law]

The problem is the migration agent is require for plesk 7.6. Whereby currently not available at server. We have follow the tutorial given from website under /admin/help/tutorials/?tutorial-anchor=pmm#pmm-migrate-data-from-windows-platforms. We encounter error message below:

Error: Connection to host is not available or migration agent is not running on the source host

 

[IgorG]

Why you can't upgrade these very outdated Plesk 7.6 to Plesk 9.x, for example, and then perform migration? In this case migration agent for Plesk 7.6 will not be so necessary.

 

[Law]

Hi Igor,
Are you referring to upgrade our existing windows plesk 7.6 to later version such as 8.x or 9.x? Then the migration tools/agent will available for both version? From there we can migrate out those customer from window 2003 to new server (window 2008- plesk 12).

How to upgrade our existing Plesk 7.6 (window 2003) to later version like 8.x or 9.x?

FYI, we already build a new server with windows 2008 with Plesk 12.

Regards,
Law

 

[IgorG]

Are you referring to upgrade our existing windows plesk 7.6 to later version such as 8.x or 9.x? Then the migration tools/agent will available for both version? From there we can migrate out those customer from window 2003 to new server (window 2008- plesk 12).

How to upgrade our existing Plesk 7.6 (window 2003) to later version like 8.x or 9.x?

Yes, you are correct. These versions are EOLed and not supported long time ago. Especially 7.x.
Just try to run autoinstaller and check that you can perform upgrade.

 

[eug]

hi Law,

There might be solution that will allow you to migrate directly from 7.6 into 12.5 without any intermediate steps like upgrades or 2-step migration through Plesk 9.x. The solution is in the stage when we are looking for adopters. If you are interested, please start private conversation with me.

 

[ahmet hassan]

using Plesk's built-in Migration Manager, so you can easily migrate your websites from one DV server to another.

You may also be able to use the Migration Manager to move sites from other hosting companies - if they use Control Panel software such as Plesk, cPanel, Ensim, or Hsphere.
There are a few things you will need before you can migrate to your new DV server 4.0:

• A domain name or IP address that resolves to your old server.
• The root password for your old server. If you are migrating from another (mt) Media Temple DV server, see DV:Enable root access.
• A shared IP (as opposed to exclusive) available on your new server. See DV 4.0lesk shared and exclusive IPs for details.
• Your IP address should also be set to shared on old server. See DVlesk shared and exclusive IPs.
• If sub-domains in Plesk have unique FTP users, you will encounter PMM failures with the following message:

<execution-result status="error"><message code="InternalDtdValidationFailed" severity="error"><context>void plesk::validateSchema(plesk::tXmlDocument&, const std::string&)</context><file>./xml_parse.cpp</file><line>412</line><text>Failed validation of the document with its internal DTD. The errors are: Element 'ftpusers': This element is not expected. Expected is ( sites )..</text></message></execution-result>


The obvious work around to allow complete migration is to log into Plesk on the DV 3.5, edit the sub-domains that have unique FTP users, and set them to "Use the FTP user account of the main domain". Once all of the sub-domains have been set to use the parent domain's FTP user account, the failed PMM migration will need to be removed from the PMM page, and the migration started over. The new PMM migration should be able to complete (assuming all sub-domain FTP users are set to use the "main domain's" FTP user).