We have a VM, that was unexpectedly shut down, after backup (with warnings), but snapshot consolidation looks like it failed and messed the configuration file .vmx. It pointed the VM HDD to file »WINVM-000003.vmdk« that didn't exist. There were files with numbers -000001, -000002 and -000004.
However that would be kind a normal, if our VM's name would't be »WINVM-000001« . I know that VMWare is using the extension -000001 for snapshots. But i never saw that such naming would be not recomended.
Is there an odd chance, that during the snapshot consolidation performed by Veeam when finishing the backup, that somehow last part of original name of VM was mistaken for the first snapshot. And when consolidation failed, Veeam created new snapshot »WINVM-000002« and then also 3 and 4 and then it all ended with misconfigured . vmx file and with lock on original VM file »WINVM-000001.vmdk«
Has anyone ever encountered a problem like this (or are we the first winners…) ?
- After unlocking the files, we were able to import the VM back to VC and after reconfiguration of the disks using the original file »WINVM000001.vmdk«, it started and is working normally.
- I performed a restore from the last backup and I got out files WINVM-000001.nvram, .vmdk, .vmx, .vmxf and WINVM-000001-flat.vmdk, that has a size of the 60GB, and was also able to do a FLR, so the backup is obiously in consistent state.
- We didn't open a support case... we are still gathering all the info
- And please don't ask me how in the world we choose a »lucky« name like this…