• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Migration stuck at 0%

B

Ballyhoo

Guest
Migration stuck

Hi All,

I have been gradually migrating sites from an old Plesk 7.5.4 machine to a new server running Plesk 9.5.2 (both Linux machines) for some time now but suddenly this week it's stopped working. I enter the details of the old server, it connects and lists the clients and domains that I can transfer, I select just one (any one) click through to start the transfer and the migration never gets past 0%. There are no log files being produced in /usr/local/PMM/logs I assume because the migration hasn't even got that far!

Can anyone help? Or even suggest an alternative way to transfer the sites?
 
Last edited by a moderator:
Just to add some more detail to this, I've now discovered that the old machine seems to be running out of disk space on the /dev/hda1 partition when the migration is initiated from the new server. I assume it is running out of space when creating the migration files (these are very small sites I'm trying to migrate by the way). Is there any way I can change the directory that Plesk is using to store these files before migration?
 
migration disk space

When running migration from 9.3, the target machine always creates the files in /migration, even
if in the interface you specify a different destination. So you might have a look there.

I've found that the fixes in 9.3 migration manager are worth the trouble of upgrading.
 
Back
Top