I noticed the other day that all of our VM's that get backed up by Veeam Backup and Recovery had configuration issues and were displaying "Virtual machine disks consolidation needed."
This coincided with poor VM performance accross all of the VM's affected - so i thought that (even though Veeam had competed sucessfully) the snapshots must have failed to be removed after being backed up. This was verified by seeing vmdisk-0000001.vmdk in the datastores for all of the machines affected, however, in snapshot manager it shows no snapshots.
If i try and consolidate whilst the VM is on it fails with "The maximum consolidate retries was exceeded for scsi0:0.
If i switch the VM off and consolidate it goes through and removes the snapshot disks... happy days, however the next time Veeam runs it leaves the VM's in the same "needing consolidation" state.
I tried rebooting the host ESXi 5.5 and recreating a new Veeam backup job but still the snapshots arent properly removed.
So, to try and rule Veeam out of the equasion i tried creating a new snapshot on one of the VMs through snapshot manager and then deleting it. This said it had completed sucessfully but looking at the datastore i am seeeing vmdisk-0000001.vmdk and alarm saying that "Virtual machine disks consolidation needed."
As i didnt want to mess around too much with the production environment - i have cloned one of the VMs, and re-run the Create Snapshot / Remove Snaphot which again completes sucessfully but then leaves the snapshot disk behind and asks for disk consolidation.
Running out of ideas here - has anyone come accross this before?