Hello,
I have a little problem with vsphere's storage vmotion.
I am testing vsphere's storage vmotion, and I found out that it somehow
always leaves something behind on the old datastore.
The VM that I am trying to move is called "MSCS1" has 1 disk of 10 GB.
I am trying to migrate this vm's storage from a datastore called ESXDATASTORE1 to another datastore called ESXDATASTORE2
When checking where the VM's files are currently stored uing the summary tab,
it states that this VM is on ESXDATASTORE1.
I decide to move this VM's storage to ESXDATASTORE2:
I choose the option "change datastore"
I select ESXDATASTORE2 as destination
In the advanced options I also select datastore ESXDATASTORE2 as destination for "configuration file"
and for "Hard Disk 1"
For the disk format I select "same format as source"
When the storage vmotion completes however,
I have the following problem:
In the summary tab of the vm properties,
when I check on which datastore the vm is rightnow,
it says that it now has data on both datastores:
ESXDATASTORE1 and ESXDATASTORE2.
however, when I browse datastore ESXDATASTORE1,
there seems to be nothing left of VM "MSCS1" on there, the folder "MSCS1" is gone.
when I browse ESXDATASTORE2, all files of VM MSCS1 seem to be there.
Does anybody have an idea which data of this VM is staying behind on ESXDATASTORE1 and where?
Why does the information in the summary tab show that the data of VM MSCS2 is now on 2 datastores?
is this a bug?
If I would remove datastore ESXDATASTORE1 now,
would vm MSCS1 still be functioning?
Has anybody else run into this?
Is this some kind of bug?
Or am I just doing something wrong here?
