VM integrity check necessary when moving/copying between datastores

[cookieme]

This might be a silly question, but when you move or copy a VM from one datastore to another is it necessary to run some type of verification on the VM? For instance, when downloading a file from the internet the source might publish an MD5 checksum that you can use to validate that the file has downloaded correctly. I know that a VM is composed of several files, but is there something similar for VMs?

The reason I'm asking is that when using a backup script such as ghettoVCB or manually copying a VM whether it is hot or cold is it enough to power up the VM to make sure that it works properly? Is there any room for corruption of primarily the VMDKs during a move or copy?

Thanks

[jidhin]

AFAIK, When a VM is moved or hot cloned between datastores there is minute chance for corruption. Even there is failure in hot clone due to bandwidth or datastore load you will still have the VM intact in the source.

There will not be any chance for vmdk corruption in any case.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!

[cookieme]

AFAIK, When a VM is moved or hot cloned between datastores there is minute chance for corruption. Even there is failure in hot clone due to bandwidth or datastore load you will still have the VM intact in the source.

There will not be any chance for vmdk corruption in any case.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!

Can anyone confirm this? Provide some more details?

Thanks