1 person found this helpful
Hmmm, how you modify the parent disk?!? Of course this is not normal situation, you must not manipulate the destination disks and/or VM in order to proceed normally...
That's what is strange. Nobody was even here (Sunday evening) when the disks were supposedly modified?
I'll check to see if another application was trying to run a snapshot on Sunday night.
Thanks for the input
Forgot about this thread. Answering my own question here.
A 3rd party backup application was automatically trying to backup the newly created VM (& every VM in the environment) before it had completed.
We've stopped the auto backup for every VM that enters the environment to avoid this in the future.