Migration Agent for PLESK 9.3 ?

[Peter Cassar]

Hi,

We have upgraded all our new PLESK servers to the latest Windows version (PLESK 9.3).

Now I'm looking to download the Migration Agent for PLESK 9.3 so we can continue to migrate our customers from an old PLESK 8.6 to our new PLESK 9.3. I have take a look into this page: http://www.parallels.com/download/plesk/utilities/

But I can't find it...

Thanks for your help.

Regards,

Karl

 

[IgorG]

http://download1.sw-soft.com/Plesk/PPP9/Windows/9.3.0/091222.06/migration-agent.msi

 

[Beto]

Hello,

I've installed the version mentioned above but the migration doesn't work.
I get following error:

- Network connection failed. Cannot connect to Plesk Migration Agent on the remote host

There is no problem with the network/firewall, all traffic between the servers is allowed. (Windows shares between servers works fine).

I try to migrate from Plesk 8.2.0 and 8.1.1 to 9.3.0 with the same result...

Result:

ÿÿÿÿ
 YForeignMigratorEngineCore, Version=9.300.3643.12484, Culture=neutral, PublicKeyToken=null
ForeignMigratorCore.Result
ResultCodeErrors ForeignMigratorCore.AppErrors  ýÿÿÿ   ForeignMigratorCore.AppErrors
errorsSystem.Collections.ArrayList   System.Collections.ArrayList _items_size_version  

  
 ForeignMigratorCore.AppError ErrorTypeMessage
ObjectType
ObjectName


ForeignMigratorCore.AppErrorType  ùÿÿÿ ForeignMigratorCore.AppErrorType
value__    UNetwork connection failed. Cannot connect to Plesk Migration Agent on the remote host

Any suggestions?

 

[IgorG]

When you see the error:

Network connection failed. Cannot connect to Plesk Migration Agent on the remote host

It means that PMM addresses to wrong NIC. The workaround here is to disable local area network connection and do a migration on external IP instead.
Also following KB article can be useful - http://kb.odin.com/en/1432

 

[Beto]

I've done this already but it didn't help.
I tried to let the PMM agent listen on the external address by adding it in the config file(WINAgentMng.exe.config)

<add key="IPAddress" value="" />

but after restarting PMM the config file is cleared and the default config is back.

 

[IgorG]

We have already submitted bug regarding this issue. There is following workaround from developers:

1. Disable second network connection with private IP address like '10.13.0.49'.
2. Restart PMA process - simple 'Stop' and 'Start' isn't enough.

 

[Beto]

This got me one step further:

Error: pmm utility 'migration_handler' raised an exception. Error code is: 1
See pmmcli.log to find out detailed information on this

I found this post but no solution:

http://forum.parallels.com/showthread.php?t=97694

 

[IgorG]

Try this workaround an update thread with results, please.

 

[Beto]

I was able to start a migration.

- I need to install the PMM agent mentioned above
- Disable the internat network interface
- Patch the PMM on source and target server

Thanks for the support and I hope that the bugs will be fixed asap