• 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 insufficient space?

add1

New Pleskian
I was trying to use the migration manager to transfer data from plesk 9.5.4 to 11.5.30 and before transfering, I got this weird message:

Insufficient disk space on the source server to store temporary files for transfer. Available: 255610 MB. Required: 357779 MB. Please free disk space on the source server.

How can this be possible if you're claiming you're now using rsync transport as a default (and only) option? On the source server there is about 550 GB of data, so I cannot imagine where the 357779 MB comes from? Is this only a cosmetic error or will the transfer really fail?
 
Migration agent initiative comes from source server, i.e. 9.5.4, where rsync transport is not used by default. Therefore I recommend you follow this instruction before starting migration.
 
Which instruction? :) How can I tell which transport is being used by the migration agent?
 
And how do I do that? Perhaps just delete a few customers? They will soon leave anyway considering what Parallels is doing to us...

So there is no way to use rsync transport when migrating from 9.5.4?
 
Back
Top