• 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.

Issue Slow migration

sebgonzes

Silver Pleskian
Hello

I know that there is various post about this, but all seem old...
We are migrating about 300 domains name from one servers with SSD RAID10 disk, to other with same disks, and both have an 10Gb networks.
Data are about 120G
Migration works but the duration is very very hight, +/- 7/8 hours, no heavy load in none of server (source or target), when there is a heavy data to transfer, all go very fast, but seem to loose a lot of time creating or checking object, is there any way to speed this?? it's a bit frustrating this time with the hardware that we use...
 
Are they both on 12.5 or higher? There was some major changes to the migration tool around this time which speed things up.
 
Last edited:
First in plesk onyx 17.0.17 and newer (target) plesk 17.5.3... And yes, 10 domains at same time, but still very very slow...
 
Right, the "Restore hosting settings of subscription" process can be performed only by one subscription at one time. There are some another processes which cannot be executed parallely and they slow down speed of migration too.
Exactly to solve these limitations Plesk migrator has a sync of content feature. You can transfer all objects slowly and then fastly sync content finally before switching of DNS.
 
Right, the "Restore hosting settings of subscription" process can be performed only by one subscription at one time. There are some another processes which cannot be executed parallely and they slow down speed of migration too.
Exactly to solve these limitations Plesk migrator has a sync of content feature. You can transfer all objects slowly and then fastly sync content finally before switching of DNS.

So you recomand to firstly do an migration of only "object" and then "all contents" ?
 
We are recommend the following process:

1. Notice clients that they will be migrated and to recommend do not do any changes in Plesk for minimize lost of data.
2. Transfer all objects and data to new server. This step could be take many time.
3. Perform sync of content and switch DNS on the time when server load is minimal.On this step all data will be synced and only databases will be transferred again.
4. Sync mail content again and notice clients that migration was finished.
 
We are recommend the following process:

1. Notice clients that they will be migrated and to recommend do not do any changes in Plesk for minimize lost of data.
2. Transfer all objects and data to new server. This step could be take many time.
3. Perform sync of content and switch DNS on the time when server load is minimal.On this step all data will be synced and only databases will be transferred again.
4. Sync mail content again and notice clients that migration was finished.

Sorry Mr.D, but there is no way to do this massively with all suscriptions???
I can migrate all suscription without data, but to sincronize data, I had to pulse sincr on each domain name??
 
Back
Top