We recently performed multiple live storage vmotions in order to upgrade our datastores. The svmotions completed successfully but shortly after (30minutes - 2days) we received notification from the customers that the DB had been corrupted. We opened a ticket with support but support does not think that svmotion caused the DB corruptions because the corruptions were not immediately noticed after the svmotion. Later we received notification from an application owner that 2 days after we svmotioned their VMs they noticed application issues.
Has anyone else experienced guest OS corruptions after live svmotions?
SvMotion can't root cause of this, because VM's files moving during storage migration and if there is any problem, all files will be damaged.
I had a similar problem.
I was looking for decision and found this:
vmotion & chapshots uses Change Block Tracking (CBT)
you can help it: