This morning in vCenter one of my VM's was flagged with a warning that it needed consolidating. I have been attempting to consolidate it without having any luck so far. I am running two Esx5.1 hosts.
First I tried to consolidate from snapshot manager and I got an error about locked files ("Unable to access file <unspecified filename> since it is locked."). Viewing the vm folder containing this VM on my San and I can see a lot of delta vmdk files, and a lot of ctk vmdk files. The first of these were last modified yesterday at 13:30, most of them were modified today at 13:30 (13:30 is when the backup runs for this particular VM).
Next I created a new snapshot (successful) and then tried to delete all snapshots (also successful) - but it did not remove any of the orphaned snapshots in the vm folder.
I tried restarting the mgmt. services on the ESX host.
I have restarted the VM today - it restarts fine, windows is working ok on it, and I know it is definitely still ok as it is the DC and my network is still running ok!
I have opened a support call with my virtual backup vendors (Veeam) as I thought the issue might have been caused by a backup that did not complete correctly (veeam backup uses the VMware snapshots), but the veeam backups are running with no errors, they are creating a snapshot for the backup and then deleting it at the end of the job - the veeam backup for that server ran ok today at 13:30.
I have looked at the VMware.log for the vm I'm concerned about, I don't understand it fully - but I can't see any errors, or any mention of locked files.
From google I can only find one mention of locked files which sounds like mine: - and I have already tried all the fixes in this support doc.
All other mentions of vmare and locked files seem to be talking about vm's that don't turn on - in this case the vm is running and seems to be fine (I installed 4 windows updates this morning and restarted
before I realised it had a VMware error).
Does anyone have any ideas of how to fix this? I'm not sure what to try next....
First I tried to consolidate from snapshot manager and I got an error about locked files ("Unable to access file <unspecified filename> since it is locked."). Viewing the vm folder containing this VM on my San and I can see a lot of delta vmdk files, and a lot of ctk vmdk files. The first of these were last modified yesterday at 13:30, most of them were modified today at 13:30 (13:30 is when the backup runs for this particular VM).
Next I created a new snapshot (successful) and then tried to delete all snapshots (also successful) - but it did not remove any of the orphaned snapshots in the vm folder.
I tried restarting the mgmt. services on the ESX host.
I have restarted the VM today - it restarts fine, windows is working ok on it, and I know it is definitely still ok as it is the DC and my network is still running ok!
I have opened a support call with my virtual backup vendors (Veeam) as I thought the issue might have been caused by a backup that did not complete correctly (veeam backup uses the VMware snapshots), but the veeam backups are running with no errors, they are creating a snapshot for the backup and then deleting it at the end of the job - the veeam backup for that server ran ok today at 13:30.
I have looked at the VMware.log for the vm I'm concerned about, I don't understand it fully - but I can't see any errors, or any mention of locked files.
From google I can only find one mention of locked files which sounds like mine: - and I have already tried all the fixes in this support doc.
All other mentions of vmare and locked files seem to be talking about vm's that don't turn on - in this case the vm is running and seems to be fine (I installed 4 windows updates this morning and restarted
before I realised it had a VMware error).
Does anyone have any ideas of how to fix this? I'm not sure what to try next....