• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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