VMware Cloud Community
Ski473
Enthusiast
Enthusiast

Can't consolidate a snapshot for one VM - ESX 3.5.

Hi , I have a VM which when snapshotted is ok however when the snapshot is consolidated the VM hard powers down and won't start back up - with an error:

Reason: The parent virtual disk has been modified since the child was created

I can correct this by modifying the VMX file and change the start file back to the base rather than the delta ( I would have thought it would complete this as part of the consolidate process - but it does look to fail in the logs and I guess it never happens ) :

Dec 14 05:27:01.436: vmx| SNAPSHOT: Consolidating from '/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-000002.vmdk' to '/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM.vmdk'.
Dec 14 05:27:01.438: vmx| DISKLIB-VMFS : "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-flat.vmdk" : open successful (24) size = 53687091200, hd = 4015828. Type 3
Dec 14 05:27:01.438: vmx| DISKLIB-DSCPTR: Opened [0]: "deadVM-flat.vmdk" (0x18)
Dec 14 05:27:01.438: vmx| DISKLIB-LINK  : Opened '/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM.vmdk' (0x18): vmfs, 53687091200 sectors / 26214400 Mb.
Dec 14 05:27:01.438: vmx| DISKLIB-LIB   : Opened "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM.vmdk" (flags 0x18). 89C4BB4
Dec 14 05:27:01.440: vmx| DISKLIB-VMFS : "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-000002-delta.vmdk" : open successful (24) size = 52430848, hd = 4167381. Type 8
Dec 14 05:27:01.440: vmx| DISKLIB-DSCPTR: Opened [0]: "deadVM-000002-delta.vmdk" (0x18)
Dec 14 05:27:01.440: vmx| DISKLIB-LINK  : Opened '/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-000002.vmdk' (0x18): vmfsSparse, 53687091200 sectors / 26214400 Mb.
Dec 14 05:27:01.441: vmx| DISKLIB-VMFS_SPARSE :Can't create deltadisk node 3f96d5-deadVM-000002-delta.vmdk failed with error The operation completed successfully
Dec 14 05:27:01.441: vmx| DISKLIB-LIB   : Opened "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-000002.vmdk" (flags 0x18). 88E2604
Dec 14 05:27:01.441: vmx| DISKLIB-LINK  : Attach: Content ID mismatch (fcf6ef35 != 0d5c7eaa).
Dec 14 05:27:01.441: vmx| DISKLIB-CHAIN : failed to attach
Dec 14 05:27:01.441: vmx| DISKLIB-LIB   : Failed to attach 88E2604 to 89C4BB4: Chain->attach failed.
Dec 14 05:27:01.441: vmx| DISKLIB-VMFS : "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-000002-delta.vmdk" : closed.
Dec 14 05:27:01.441: vmx| SNAPSHOT: SnapshotCombineDisks failed: 5
Dec 14 05:27:01.441: vmx| DISKLIB-VMFS : "/vmfs/volumes/48bc3694-28959c38-5d31-001a64c32812/VeeamBackup/deadVM(64)/deadVM-flat.vmdk" : closed.
Dec 14 05:27:01.441: vmx| SNAPSHOT: SnapshotConsolidate failed 5
Dec 14 05:27:01.441: vmx| SNAPSHOT: Consolidate failed 5
Dec 14 05:27:01.446: vmx| VMXVmdb_LoadRawConfig: Loading raw config
Dec 14 05:27:01.450: vmx| Checkpoint_Unstun: vm stopped for 110291 us

I particularly like this line :

Can't create deltadisk node 3f96d5-deadVM-000002-delta.vmdk failed with error The operation completed successfully

This only appears to occur for this VM and changing the VMX allows it to boot again - however this presents a problem because I can't snapshot it and hence can't actually get a backup via our veeam backup process.

On a side note this VM has had issues in the past with the VEEAM backup process and recently when trying to replicate it the VM powered off and I had to recreate the VMDK descriptor file.  It did actually backup last night but then died due to the snapshot consolidate operation I gather.

Any ideas ?

Tags (2)
Reply
0 Kudos
2 Replies
TomHowarth
Leadership
Leadership

How big is this guest,  I would seriously consider doing a V2V of it to an new VM.  but using the P2V process so that Converter thinks it is a Physical machine.

There is something not quite right with it and the fact that you have had to mess  with VMDK descriptor files is worrisome.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
Reply
0 Kudos
Ski473
Enthusiast
Enthusiast

Yeah , was probably just going to migrate the database it holds onto another machine but thought I'd see if anyone else had come across this first.

Thanks for your input though.

Reply
0 Kudos