• 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

Issue Migration tool needs help

tkalfaoglu

Silver Pleskian
The migration tool really needs help.. The SINGLE step in the migration between two super PC's should not take hours..
1 domain, a simple single domain, and THIS step took over an hour so far, still going:


Jul 7 14:31:03 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=8863 process=8863 trace=35452:60e
5905d62e49).
Jul 7 14:31:04 ocean systemd[1]: run-plesk-task-8863.service: Succeeded.
Jul 7 14:31:04 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=8863 process=8863 trace=35452:60e
5905d62e49).
Jul 7 14:31:04 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=8864 process=8864 trace=35452:60e
5905d62e49).
Jul 7 14:31:04 ocean systemd[1]: run-plesk-task-8864.service: Succeeded.
Jul 7 14:31:04 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=8864 process=8864 trace=35452:60e
5905d62e49).
Jul 7 14:31:04 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=8865 process=8865 trace=35452:60e
5905d62e49).
Jul 7 14:31:05 ocean systemd[1]: run-plesk-task-8865.service: Succeeded.
Jul 7 14:31:05 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=8865 process=8865 trace=35452:60e
5905d62e49).
Jul 7 14:31:05 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=8866 process=8866 trace=35452:60e
5905d62e49).
Jul 7 14:31:05 ocean systemd[1]: run-plesk-task-8866.service: Succeeded.
Jul 7 14:31:05 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=8866 process=8866 trace=35452:60e
5905d62e49).
Jul 7 14:31:05 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=8867 process=8867 trace=35452:60e
5905d62e49).
Jul 7 14:31:05 ocean systemd[1]: run-plesk-task-8867.service: Succeeded.
Jul 7 14:31:05 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=8867 proces
 
Well, how much space is occupied by the subscription? And how many files?

The initial sync can take several hours, depending on the amount of data and number of files. From my own experience, the initial sync for 300 domains, 400GB of data and 4 million files takes about 6-7 hours.

The update-sync (the step you do just before switching to the new server) is a lot faster of course, depending on the amount of changed data between the initial sync and the update.
 
It's a small subscription, but I believe it has many (mailman) mailing lists of several thousands EACH.
It seems the migration tool is telling the other tool to "add this email address to that mailing list" one by one.. o_O
Each email seems to take 10 seconds, so I am estimating 27 HOURS to migrate this one subscription..
 
Actually it takes less than that -- maybe 2 seconds each.. so I am revising it to take about 5 hours.
 
This will only be done during the initial sync. The refresh will be much quicker.

So I suggest you let it run until it's finished and then you do a refresh and measure the time it takes again.
 
Back
Top