I would like to know if it's normal Processing rate for quick migration job (after instant vm recovery) is always 0KB/s and bottleneck is detecting until the end of the job ?
Is it not possible to update it during the job to know what is his value ?
The situation does not look expected, so can you open a case with our support team and provide its number here? Also, it would help us, if you share the vSphere version you are currently at. Thanks!
Ok I will do it and share the number here
It s quick migration for sure. I migrated around 100 vm from hyperv to vmware with this method and number were present only if I use veeam transport for migration and not vmware.
I don't know for sure, but my guess is that this is by design -- vMotion we don't deploy datamover agents so we cannot know the data transfer amounts like we would if it goes through our datamover agents, just the % reported by VMware. Processing Rate is just a function of total data / Processing Time which is why I guess that gets populated.
I did doublecheck the relevant database table and indeed it's populated by the datamover agents, so for vMotion based Quick Migrations, the processing stats are 0, but for Veeam Quick Migrations, you have processing stats.
David Domask | Product Management: Principal Analyst