The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child

Using Veeam backups saw this with a vm this morning, vm couldnt consolidate or turn on

The parent  virtual disk  has been  modified  since the  child was  created. The  content ID  of the  parent  virtual disk  does not  match the  corresponding parent  content ID  in the child

Got it working and turned on again, with this link

https://www.geekshangout.com/vmware-the-parent-virtual-disk-has-been-modified-since-the-child-was-created-the-content-id-of-the-parent-virtual-disk-does-not-match-the-correspond-ing-parent-content-id-in-the-chil/

Is there a root cause for this, just due to Veeam backup or is it something else for us to look at ?
LVL 1
Indie101Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is there a root cause for this, just due to Veeam backup or is it something else for us to look at ?

Yes the root cause is the VM was powered on, without the snapshot attached.

and the CID on the Parent Virtual Disk gets changed, and does not match the chain in the snapshot (delta) disk.

or snapshot corruption has occurred, snapshots have been manually deleted.

Veeam Backup can leave a VM running on a snapshot, but does not cause this error directly.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Indie101Author Commented:
Thanks could it be as well that there are stale snapshot files left after a Veeam backup ,during the next backup there would be other snapshot taken which may cause this mis-match.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Not that we've seen, but anything could happen with snapshots involved, make sure you regularly check after backups no snapshots exist.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.