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

Input Migrator Re-Sync wastes time at "Fetch configuration data from Plesk servers" every 5 subscriptions

websavers

Regular Pleskian
When we run a re-sync with Plesk migrator to refresh the data at the destination, prior to 'flipping the switch' over to the new server, for every 5 subscriptions it does this for about 3-4 minutes:

Overall - Fetch configuration data from Plesk servers

Presumably it's grabbing info on the *next* 5 subscriptions. However since we have to block access to the server to run the differential (to ensure nothing is changed on the source server during migration), that means things are down longer than necessary because of this. I would like to see it Fetch configuration data for *all* subscriptions in the queue at the start of the re-sync, as we don't have to block access to the server during that part of the process. Once it actually moves on to copying data from the subscriptions, we would then block access.

This kind of change should make the migration re-sync time faster, and would definitely make the length of downtime faster.
 
Back
Top