So this has been an ongoing saga for quite a while:
This is an issue I blogged about a little while ago too, right here:
It has been causing people plenty of issues and although it’s simple to fix, it’s annoying and it shouldn’t be happening!
Veeam and VMware have been pointing the finger at each other for months now. Personally I would lean to it being a VMware issue, simply because a restart of the management agents resolves the issue.
So I have been following the thread on the Veeam forums and there has finally been an update!
VMware have now released a patch which seems to fix this issue:
so if you are on 5.5 you need to go to at least:
|ESXi 5.5 Patch 8||2016-08-04||4179633|
If you are on 6.0 you need to go to at least:
|ESXi 6.0 Patch 3||2016-08-04||4192238|
Veeam now recommend you roll it out and see if the issue persists.
So for me, since we are currently on 5.5u3b, we need to go to at least patch 8.
This patch has another bonus for us. Every so often when I am upgrading VM hardware and power on the VM again I have sporadically come across the ‘CID mismatch error’. There are ways around this but it can be a bit hit and miss. Half the time it was just easier to restore from a Veeam backup or use a SAN snapshot to sort it out. Well it looks like patch 8 permanently fixes it:
Attempts to power on a virtual machine after upgrading the hardware version might fail. This is an issue seen on ESXi 5.5 Update 3a or later. An error message similar to the following is displayed:
cannot open the disk vmdk or one of the snapshot disks it depends on. Could not open/create change tracking file.
But we are going to go to the latest patch:
|ESXi 5.5 Patch 9||2016-09-15||4345813|
Simply because it incorporates all the other fixes and a few more and its the latest. I currently have it in testing and can report, that so far I have not come across any issues, be it the Veeam issue or the VM H/W upgrade issue! Horrayyyyyyyyyyyyyyyyyyyyyyyy
One bonus for us being on 5.5u3b, and moving to these new patches, is we now have access to the HTML5 Host Client. Finally! It is pretty nice too, everyone who hates the normal web client loves this and it is easy to see why.
It is nice that VMware haven’t forgotten about us guys on 5.5! You can access it here:
Then select the host client to be redirected, as shown below: