• 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 Migration fails with current migrator

@mr-wolf

I personally do not have the issues, even though I can imagine a number of causes for problems with the Plesk Migrator.

In essence, your report is indicating the symptom of "random backup packages": backup files are incomplete or even inconsistent across time.

Can you indicate at which time you did the problematic migration?

And if yes, please indicate whether there were some (scheduled or regular) backups running in the background?

I am asking because the Plesk Migrator extension uses an odd combination of rsync, pigz and api access........and pigz can become a problem, in the case of multiple disk IOPS (read/write operations, for instance associated with regular/scheduled backups), with this problem often associated with the symptom "random backup packages".

Another potential explanation can be some service disruption in one of the servers: a decrease in network connectivity can result in an incomplete file list and this scenario is hence often associated with the symptom of "random backup packages".

Again another potential explanation is that one of your disks is not performing properly: hardware related failures.

Note that the latter two (alternative) explanations are very unlikely.

Anyway, I must agree............ it does not feel comfortable.

Regards........
 
This morning in a batch of 3 sites I had this. A 2nd batch didn't give this problem.....
I fixed the sites manually by creating the nginx.conf and the domain.nl.webmail.conf manually....

I can't imagine it's hardware...
It's skipping a specific logical step.
Sites are migrated one by one. All 3 had the same files missing (only nginx files).
 
@mr-wolf,

So, if we start discussing this, we have two important things to consider: a) Nginx related problems when migrating and b) random backup packages.

Are both the target and source server identical, in terms of:

- Nginx: version
- OpenSSL: version installed and version used to compile Nginx
- Plesk version (note: this is more or less an obvious question, I assume that Plesk is identical - but still have to ask)

In essence, I am rather interested in this particular issue, since it will prove hard to reproduce.

Regards........
 
Back
Top