Just trying to get an understanding of using Storage vMotion and the results. We have some VM's that have had disks dropped and then added to a new VM. The original and new VM's are on different datastores. The disks are not shared between VM's - there is a one to one relationship. Now we would like to storage vMotion to a different datastore and want to understand what the impact is before attempting this.
Original datastore File Moving to datastore
ds1 vmdk1 ds3
ds2 vmdk2 ds3
Is this type of move supported using Storage vMotion? In the end, do all the vmdk's end up residing in the same virtual machine directory? I'm thinking yes, but in a quick search I haven't seen a clear article that addresses this scenario.
Thanks in advance.