Nice, isn’t it? Creating a new snapshot and selecting delete all snapshots will not work because it’s still locked. This info is now only found in the vmware.log file (and surely vmkernel log files) of the VM in its datastore: # grep -i lock vmware.log Pre-vSphere 5, the task would fail with an error about how it couldn’t consolidate the snapshot due to a locked file. The remove snapshot task completes successfully and you’ll only notice on the VM summary page that it needs disk consolidation. Unfortunately, unlike with vSphere 4 there is no obvious, specific error. You will not see these snapshots in the snapshot manager (fix this for good, VMware!), but only on the filesystem. In vCenter, the warning “Virtual machine disks consolidation failed.” is being logged as a simple event (I might create an alarm for this now that I think about it). We are currently facing an issue with a small number of VMs, where snapshots created by our backup software, Symantec BackupExec, can’t be removed properly because of locked files (neither through BackupExec nor manually). The issue is now finally resolved since our backup admins upgraded to Backup Exec 2010 R3 Service Pack 3. We’re also still using Backup Exec 2010 R3.
The case at Symantec never got resolved to this very day. Check out the comments after reading this article, some interesting points there.
0 kommentar(er)
