Only difference is the ESXi host they are running on, but that same ESXi host with the VM with high retries has another VM that does have the same issue. The three that I got specifics for to include in my post are the same exact image. I should add that there are only 3 total versions of this disk and the only different between the versions would be microsoft security patches, and and a few reg keys that were changed for some software we have I only even stumbled across this problem because i am trying to figure out why my images keep corrupting after applying microsoft security patches. I dont really know where to begin troubleshooting this nor am i even certain its worth spending what little time i have on. but beyond that, what else can high retries cause? and more specifically, what kind of impact could high retry counts have on a maintenance image? I understand that a high number of retries can cause performance issues on the server. while our VMware does sometimes migrate my target devices to different hosts, this never seems to correlate with high retry counts. this week its desktop_a, and next week after a round of reboots it might be desktop_d. and those targets do NOT have a high number of retries.Īdditionally, while i seem to randomly get targets with extremely high retry counts, its never the SAME target. however, the host that is running desktop_a has 2 other PVS target devices streaming a different image. The only difference that i can really tell is that all three of these targets are running on different ESXi Hosts.
I have two PVS servers that are splitting the load, but specifically the exact same PVS server is streaming to targets desktop_a (1216 retries), desktop_b (291 retries), and desktop_L (2 retries)
Target devices "desktop_C" through "desktop_L" have 7 or less retries (the target with the longest up time of 10 days has 2 retries - "Desktop_L")
Target "desktop_B" has 291 retries (also 3 days up time) Target "desktop_A" device has 1216 retries as of writing this (3 days up time) all of the targets are running the same production version of the image. all of these targets have been up between 1 and 10 days. So i have an image that streams to 12 targets.
I have yet another "fun" and completely obscure thing that i cant quite pin down how to troubleshoot properly.
0 kommentar(er)
