Problems with a restored VM: Invalid IDs in the Snapshot Files

apiVersion: soultec.ch/v1kind: Postmetadata: name: problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files locale: en labels: author: dario-doerflinger series: lessons-learned capability/virtualization: 1.37 capability/backup-recovery: 2.18 vendor/vmware: 0.88 annotations: source: blog-content/posts/en/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md route: /en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files/ schema: /nerd/schema/posts.json markdown: /en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.mdspec: title: "Problems with a restored VM: Invalid IDs in the Snapshot Files" date: 2014-11-21 author: dario-doerflinger locale: en summary: >- Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore.. capabilities: [virtualization, backup-recovery] vendors: [vmware] series: lessons-learned legacySlug: problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files migrated: 2026-08-24 draft: false sections: - body: | Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore.. Well anyways, restrore was completed but threw an error-message saying that the snapshot could not be removed. Fine by me, right? So I went to the "Snapshot Manager" and deleted all the snapshots. The task went through perfectly but another message poppep up saying "VM need consolidation". Okay, no problem. Over the GUI I tried to consolidate the disks, but that threw an error as well… Time to connect to the ESXi host directly (over ssh) and look at the problem there. I went to the datastore containing the VM (well, actually the VM was spread across seven Datastores, but you get the point) and looked at the descriptor Files of the VMs. It turned out that all the snapshot-descriptor-Files (somevm\_1-000001.vmdk) had a wrong ParentCID. It referenced itself.. The next step was to replace all the wrong CIDs with the correct CID of the parent-disk. In a VM with 16 disks spread across 7 datastores this was quite a task. After I was finished (important: double-check that you put the corrent CID in the descriptor file, otherwise you could corrupt the entire VM!) all I had to do was to re-register the VM into the inventory. It then recognised the snapshot again, and the consolidate task went through without any errors. That's it. Wrong CID in the descriptor files of the VM were resolved and we were able to strart the VM again.status: corpus: 267 alsoLike: - {ref: posts/backing-up-fault-tolerance-protected-vms-the-operation-is-not-supported-on-the-object, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/addon/site-recovery-manager, score: 1.00} - {ref: experts/marco-betschart, score: 0.74}

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/virtualization": "1.37", "capability/backup-recovery": "2.18", "vendor/vmware": "0.88" }, "annotations": { "source": "blog-content/posts/en/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md", "route": "/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md" } }, "spec": { "title": "Problems with a restored VM: Invalid IDs in the Snapshot Files", "date": "2014-11-21", "author": "dario-doerflinger", "locale": "en", "summary": "Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore..", "capabilities": [ "virtualization", "backup-recovery" ], "vendors": [ "vmware" ], "series": "lessons-learned", "legacySlug": "problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files", "migrated": "2026-08-24", "draft": false }, "sections": [ { "body": "Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore..\n\nWell anyways, restrore was completed but threw an error-message saying that the snapshot could not be removed. Fine by me, right? So I went to the \"Snapshot Manager\" and deleted all the snapshots. The task went through perfectly but another message poppep up saying \"VM need consolidation\". \n \nOkay, no problem. Over the GUI I tried to consolidate the disks, but that threw an error as well…\n\nTime to connect to the ESXi host directly (over ssh) and look at the problem there. I went to the datastore containing the VM (well, actually the VM was spread across seven Datastores, but you get the point) and looked at the descriptor Files of the VMs.\n\nIt turned out that all the snapshot-descriptor-Files (somevm\\_1-000001.vmdk) had a wrong ParentCID. It referenced itself..\n\nThe next step was to replace all the wrong CIDs with the correct CID of the parent-disk. In a VM with 16 disks spread across 7 datastores this was quite a task. After I was finished (important: double-check that you put the corrent CID in the descriptor file, otherwise you could corrupt the entire VM!) all I had to do was to re-register the VM into the inventory. It then recognised the snapshot again, and the consolidate task went through without any errors.\n\nThat's it. Wrong CID in the descriptor files of the VM were resolved and we were able to strart the VM again." } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/backing-up-fault-tolerance-protected-vms-the-operation-is-not-supported-on-the-object", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/site-recovery-manager", "score": "1.00" }, { "ref": "experts/marco-betschart", "score": "0.74" } ] }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files"locale = "en"[metadata.labels]author = "dario-doerflinger"series = "lessons-learned""capability/virtualization" = "1.37""capability/backup-recovery" = "2.18""vendor/vmware" = "0.88"[metadata.annotations]source = "blog-content/posts/en/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md"route = "/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md"[spec]title = "Problems with a restored VM: Invalid IDs in the Snapshot Files"date = 2014-11-21author = "dario-doerflinger"locale = "en"summary = "Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore.."capabilities = ["virtualization", "backup-recovery"]vendors = ["vmware"]series = "lessons-learned"legacySlug = "problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files"migrated = 2026-08-24draft = false[[sections]]body = '''Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore..Well anyways, restrore was completed but threw an error-message saying that the snapshot could not be removed. Fine by me, right? So I went to the "Snapshot Manager" and deleted all the snapshots. The task went through perfectly but another message poppep up saying "VM need consolidation". Okay, no problem. Over the GUI I tried to consolidate the disks, but that threw an error as well…Time to connect to the ESXi host directly (over ssh) and look at the problem there. I went to the datastore containing the VM (well, actually the VM was spread across seven Datastores, but you get the point) and looked at the descriptor Files of the VMs.It turned out that all the snapshot-descriptor-Files (somevm\_1-000001.vmdk) had a wrong ParentCID. It referenced itself..The next step was to replace all the wrong CIDs with the correct CID of the parent-disk. In a VM with 16 disks spread across 7 datastores this was quite a task. After I was finished (important: double-check that you put the corrent CID in the descriptor file, otherwise you could corrupt the entire VM!) all I had to do was to re-register the VM into the inventory. It then recognised the snapshot again, and the consolidate task went through without any errors.That's it. Wrong CID in the descriptor files of the VM were resolved and we were able to strart the VM again.'''[status]corpus = 267[[status.alsoLike]]ref = "posts/backing-up-fault-tolerance-protected-vms-the-operation-is-not-supported-on-the-object"score = "1.00"[[status.alsoLike]]ref = "solutions/vmware/vmware-cloud-foundation/addon/site-recovery-manager"score = "1.00"[[status.alsoLike]]ref = "experts/marco-betschart"score = "0.74"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <series>lessons-learned</series> <entry key="capability/virtualization">1.37</entry> <entry key="capability/backup-recovery">2.18</entry> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>blog-content/posts/en/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md</source> <route>/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files.md</markdown> </annotations> </metadata> <spec> <title>Problems with a restored VM: Invalid IDs in the Snapshot Files</title> <date>2014-11-21</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore..</summary> <capabilities> <item>virtualization</item> <item>backup-recovery</item> </capabilities> <vendors> <item>vmware</item> </vendors> <series>lessons-learned</series> <legacySlug>problems-with-a-restored-vm-invalid-ids-in-the-snapshot-files</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> </spec> <sections> <section> <body>Recently we've had the pleasure to restore a Database-VM from the most recent Backup because one of my coworkers accidentally deleted a vital .vmdk File on the datastore..Well anyways, restrore was completed but threw an error-message saying that the snapshot could not be removed. Fine by me, right? So I went to the "Snapshot Manager" and deleted all the snapshots. The task went through perfectly but another message poppep up saying "VM need consolidation". Okay, no problem. Over the GUI I tried to consolidate the disks, but that threw an error as well…Time to connect to the ESXi host directly (over ssh) and look at the problem there. I went to the datastore containing the VM (well, actually the VM was spread across seven Datastores, but you get the point) and looked at the descriptor Files of the VMs.It turned out that all the snapshot-descriptor-Files (somevm\_1-000001.vmdk) had a wrong ParentCID. It referenced itself..The next step was to replace all the wrong CIDs with the correct CID of the parent-disk. In a VM with 16 disks spread across 7 datastores this was quite a task. After I was finished (important: double-check that you put the corrent CID in the descriptor file, otherwise you could corrupt the entire VM!) all I had to do was to re-register the VM into the inventory. It then recognised the snapshot again, and the consolidate task went through without any errors.That's it. Wrong CID in the descriptor files of the VM were resolved and we were able to strart the VM again. </body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/backing-up-fault-tolerance-protected-vms-the-operation-is-not-supported-on-the-object</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/site-recovery-manager</ref> <score>1.00</score> </item> <item> <ref>experts/marco-betschart</ref> <score>0.74</score> </item> </alsoLike> </status></manifest>

Problems with a restored VM: Invalid IDs in the Snapshot Files

You might also like

Backing up Fault-Tolerance protected VMs (the operation is not supported on the object)

Site Recovery Manager

Marco Betschart