When I triggered storage vmotion of a VM from a local datastore to a shared datastore, I end up in a weird situation where the VM now has dependencies on both the datastores. I seen some DVMotion delta files around. This is on ESX 3.5.
Is there a way around it?
The storage vmotion may have failed. what happens is it starts by making a snapshot on the destination server, and it commits all the data. If it gets interrupted, it gets left in a weird state.
So to try and fix it means you shut off the VM, and right click, there should be an option to resume data migration.
You could also check and make sure that the VM doesn't have an ISO mounted on the old datastore.