• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Plesk Migrator wants to store data in C-drive, but configured to use different drive

kenneth-vkd

Basic Pleskian
Server operating system version
Windows Server 2022
Plesk version and microupdate number
18.0.54
Hi
We are in the proces of migrating a set of sites from a Windows 2016 with Plesk Onyx to a Windows 2022 with Ples Onyx.
We have a small difference in the configuration of the two servers, as the old one has one large 2.2TB drive (the limit when using MBR disk and legacy BIOS). This one drive (although backed by RAID and full system backups) holds the OS, applications, Plesk and all websites.
In the new server, we have done it a little different, as we have the C-drive for just the OS and Plesk and during setup, we configured plesk to store userdata and websites on the P-drive.

When attempting the migration of a site, we get the following warning message:
Insufficient disk space on the destination server to transfer all the selected subscriptions. Available: 104333 MB. Required: 1697128 MB. Note that the required space is calculated as a sum of web, mail, and database contents of domains. The required space is calculated once a day and stored in cache, so the actual size of domains might differ from the calculated size. If you make sure that the selected domains do not occupy more space than available, you can proceed with transfer.
Please free disk space on the destination server.
The C-drive as a 128GB drive and has around 100GB of free space, while the P-drive (supposed to contain all the data) is 3000GB

Is this just a bug in the tool or will it actually attempt migration to the C-drive?
 
That would be an awkward behavior. Not sure whether it is a bug or a configuration issue. Have you checked that the Plesk vhost root is on your P: drive?
 
That would be an awkward behavior. Not sure whether it is a bug or a configuration issue. Have you checked that the Plesk vhost root is on your P: drive?
Checked it using your guide and the location is listed as "P:\Inetpub\vhosts\" on the target server.

I am tempted to just attempt running the migration of a single subsription that is larger than the C-drive. Just to see if it is a bug in the premigration check, but the actual migration respects the configured vhost root
 
Checked it using your guide and the location is listed as "P:\Inetpub\vhosts\" on the target server.

I am tempted to just attempt running the migration of a single subsription that is larger than the C-drive. Just to see if it is a bug in the premigration check, but the actual migration respects the configured vhost root
Seems to a bug in the premigration checks.
Just started the migration of a single subscription totalling around 1500G and over 100GB have already been transferred
 
Back
Top