I’m not sure if this is an existing issue or new, however, when doing a Quick Migration in VBR 12.1, I see no processing rate of the job when completed. In VBR 11, we would get a XYZ MB/s or GB/s in that “area”. Any ideas? Can this be found in logs? Some DB table (how to connect to DB if so)?
Best answer by jaceg23
View original
+4
It should show the processing rate.
Althought it’s possible see this info in the logs, I would suggest open a case with Veeam SUpport because this is not normal.
+17
What about the History node and viewing job details?
+4
I did a quick test here and it’s showing the processing rate:
I’m using the last build (12.1.1.56). Are you using this build?
+20
I did a quick test here and it’s showing the processing rate:
I’m using the last build (12.1.1.56). Are you using this build?
I was about to say it should show processing rate.
I did a quick test here and it’s showing the processing rate:
I’m using the last build (12.1.1.56). Are you using this build?
On Build 12.1.0.2131, not yet on that build :/. Should it work on this build?
What about the History node and viewing job details?
Nope, same there. However, I was once at v11 and the jobs I did then show in history and have the PR.
It should show the processing rate.
Althought it’s possible see this info in the logs, I would suggest open a case with Veeam SUpport because this is not normal.
From my knowledge, there’s only one log for migration, and I do not see anything in there right offhand for speed, I’m still digging however.
+20
I did a quick test here and it’s showing the processing rate:
I’m using the last build (12.1.1.56). Are you using this build?
On Build 12.1.0.2131, not yet on that build :/. Should it work on this build?
Should work on this build too.
If my math is right 🤣…
3h 22m 5s (12125 s), 4.8 TB (5033164.8 MB), ~415 MB/s
+4
It should show the processing rate.
Althought it’s possible see this info in the logs, I would suggest open a case with Veeam SUpport because this is not normal.
From my knowledge, there’s only one log for migration, and I do not see anything in there right offhand for speed, I’m still digging however.
There is actually a few logs because this involves read the source data and transfer to target host.
In my case, my VBR server is my proxy, so I have all the logs here: C:\ProgramData\Veeam\Backup\Quick_Migration_Job
Here a screenshot of my folder:
If you have different proxies you should see the logs on those servers too.
+4
If my math is right 🤣…
3h 22m 5s (12125 s), 4.8 TB (5033164.8 MB), ~415 MB/s
Are you migrating VM between ESXi servers in the same vCenter?
Maybe is using vMotion to do the migration?
Do a test and select the option “Force Veeam transport usage” and see if the processing rate will show:
Case #07142504 opened to Veeam. Sev 4.
If my math is right 🤣…
3h 22m 5s (12125 s), 4.8 TB (5033164.8 MB), ~415 MB/s
Are you migrating VM between ESXi servers in the same vCenter?
Maybe is using vMotion to do the migration?
Do a test and select the option “Force Veeam transport usage” and see if the processing rate will show:
Just doing Storage vMotion. Same host different storage. I’ll get back to you with how that goes cause I only have two big VMs at the moment for testing, this behemoth and another 1.6TB one.
+17
What about the History node and viewing job details?
Nope, same there. However, I was once at v11 and the jobs I did then show in history and have the PR.
Ugh... Interesting 😕
So on top of the PR not showing, thoughput is also not showing. And it should be showing it "live" as the VM moves. Did a "Force Veeam Transport" of a small VM and it showed PR, Throughput, and the live update graph. However, we don't want to do migrations in this manner, we want to move them using Storage vMotion as it doesn’t suspend/resume the VM, it keeps it alive.
+4
So on top of the PR not showing, thoughput is also not showing. And it should be showing it "live" as the VM moves. Did a "Force Veeam Transport" of a small VM and it showed PR, Throughput, and the live update graph. However, we don't want to do migrations in this manner, we want to move them using Storage vMotion as it doesn’t suspend/resume the VM, it keeps it alive.
Well, you opened the case, let's see what support says, but i think that because storage vmotion is doing the migration Veeam doesn't have access to those infos.
So on top of the PR not showing, thoughput is also not showing. And it should be showing it "live" as the VM moves. Did a "Force Veeam Transport" of a small VM and it showed PR, Throughput, and the live update graph. However, we don't want to do migrations in this manner, we want to move them using Storage vMotion as it doesn’t suspend/resume the VM, it keeps it alive.
Well, you opened the case, let's see what support says, but i think that because storage vmotion is doing the migration Veeam doesn't have access to those infos.
Which is strange, because in VBR11 in both test and production, it shows ¯\_(ツ)_/¯
+4
Just to be sure, I did another quick migration but this time with storage vmotion and yes, same symptom:
Unfortanately, I don’t have any lab with v11 to test. I hope support can help you with this problem
+17
Just to be sure, I did another quick migration but this time with storage vmotion and yes, same symptom:
Unfortanately, I don’t have any lab with v11 to test. I hope support can help you with this problem
Interesting. Glad you could at least replicate the behavior
+20
Just to be sure, I did another quick migration but this time with storage vmotion and yes, same symptom:
Unfortanately, I don’t have any lab with v11 to test. I hope support can help you with this problem
So potential bug in the 12.x release. Nice confirmation
Example from v11 Prod, no throughput show, no live progress tracking, but at the end it does display the PR.
+17
Example from v11 Prod, no throughput show, no live progress tracking, but at the end it does display the PR.
🤔🤔 So, somewhat normal behavior in v12 then?
+4
Example from v11 Prod, no throughput show, no live progress tracking, but at the end it does display the PR.
🤔🤔 So, somewhat normal behavior in v12 then?
The problem is not showing the processing rate on v12. Maybe Veeam changed something on how we get this info.
I had to tell the SE at Veeam to test it themselves because they asked questions like, we’ll were you watching this, watching that? Of course I was, if I wasn’t, I’d probably wouldn’t have given a 💩. They said their working on reproducing it in their lab. Til next time fellow Veeam-ers.
+20
Well hopefully they replicate it and can then fix it in a patch.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
