I've had a few VM's crash from multiple "empty" DELTA VDMK's created by the backup software. The DELTA's are empty when I examine them, although they say 120kb. I had one VM chain up to 60 before it crashed. It usually has to do with the Parent CID being incorrectly pointing in the 2.VDMK or so.
I get the following message from VI - "Cannot open the disk '/vmfs/volumes/49342342342342344534534534/ERIS/ERIS-000007.VMDK or one of the snapshot disks it depends on. Reason: The parent virtual disk has been modified since the child was created."
Is there a reason behind this and tell tale sign of eminent failure? This now happening more often and is quite tideous to resolve (if not scary to lose the entire VM.).
-
- Novice
- Posts: 6
- Liked: never
- Joined: Apr 27, 2009 2:54 am
- Full Name: Jeff Shanklin
- Contact:
-
- Novice
- Posts: 6
- Liked: never
- Joined: Apr 27, 2009 2:54 am
- Full Name: Jeff Shanklin
- Contact:
Re: Multiple "empty" DELTA VDMK's
ERIS.VDMK
# Disk DescriptorFile
version=1
CID=28daf29b
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 125967714 VMFS "ERIS‐flat.vmdk"
# The Disk Data Base
#DDB
ddb.toolsVersion = "7302"
ddb.virtualHWVersion = "4"
ddb.geometry.biosCylinders = "7841"
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
ddb.uuid = "60 00 C2 97 8e 47 7f 13‐6b 15 d1 cb cf 8b 54 1e"
ddb.geometry.cylinders = "7841"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "buslogic"
ERIS‐000001.vmdk
# Disk DescriptorFile
version=1
CID=7d4ad4c4
parentCID=7d4ad4c4
createType="vmfsSparse"
parentFileNameHint="ERIS‐000002.vmdk"
# Extent description
RW 125967714 VMFSSPARSE "ERIS‐000001‐delta.vmdk"
# The Disk Data Base
#DDB
ERIS‐000002.vmdk
# Disk DescriptorFile
version=1
CID=7d4ad4c4
parentCID=a7b1a693
createType="vmfsSparse"
parentFileNameHint="ERIS.vmdk"
# Extent description
RW 125967714 VMFSSPARSE "ERIS‐000002‐delta.vmdk"
# Disk DescriptorFile
version=1
CID=28daf29b
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 125967714 VMFS "ERIS‐flat.vmdk"
# The Disk Data Base
#DDB
ddb.toolsVersion = "7302"
ddb.virtualHWVersion = "4"
ddb.geometry.biosCylinders = "7841"
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
ddb.uuid = "60 00 C2 97 8e 47 7f 13‐6b 15 d1 cb cf 8b 54 1e"
ddb.geometry.cylinders = "7841"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "buslogic"
ERIS‐000001.vmdk
# Disk DescriptorFile
version=1
CID=7d4ad4c4
parentCID=7d4ad4c4
createType="vmfsSparse"
parentFileNameHint="ERIS‐000002.vmdk"
# Extent description
RW 125967714 VMFSSPARSE "ERIS‐000001‐delta.vmdk"
# The Disk Data Base
#DDB
ERIS‐000002.vmdk
# Disk DescriptorFile
version=1
CID=7d4ad4c4
parentCID=a7b1a693
createType="vmfsSparse"
parentFileNameHint="ERIS.vmdk"
# Extent description
RW 125967714 VMFSSPARSE "ERIS‐000002‐delta.vmdk"
-
- Veeam Software
- Posts: 268
- Liked: 63 times
- Joined: Jan 01, 2006 1:01 am
- Full Name: Stanislav Simakov
- Contact:
Re: Multiple "empty" DELTA VDMK's
Jeff, this behaviour obviously indicate some issues with your infrastructure. Probably you have to open a support call with the VMware. You can send us the VMware logs from your VM folder so that we could point you to the right direction.
Who is online
Users browsing this forum: No registered users and 85 guests