VM folder remains on datastore after migration

[MICDROP]

Hi all.

I recently moved a VM with an RDM attached to another datastore.
(After removing the RDM, only the virtual disk, drive C, was migrated. And then I re-attach the RDM on VM.)

However, as shown in the picture, the vmdk files and the rdmp.vmdk file remains on the old datastore. (With VM Folder)

The iso file is not mounted.

Because there are no vmx files on the old datastore, it doesn't look like a normal VM folder.

Is there a way to make sure it's not related to a running VM?

How do I understand the remaining vmdk files on the old datastore?
Can I remove this?

Thank you in advance!

Regards.

[tanwk]

it looks to be is your RDM pointer files that remains. I would suggest you to reattached and create the pointer files. Or do a proper storage vMotion instead of manual migrate.

[MICDROP]

@tanwk 

Hi.

Thanks for reply

I did svMotion, and the VM folder on the new datastore is filled with normal components.

"retached and created the pointer files."
-> I've detached and attached RDMs several times during VM operations. Is it because of that?

The picture below shows the VM folder in the new datastore.

I attached 6 RDMs, and they work normally.
Can I delete the pointer file?
Could you tell me why this remains on the old datastore?

Regards.

[bryanvaneeden · Accepted solution]

Hi @MICDROP,

The new folder looks alright to me, you can see it is being used because of the "~" after the .vmx file. The disks seem alright also, but like @tanwk pointed out the RDM pointer files seem to be present on the "old" location. You should move these to the new location. You can do this from the File view on the datastore.

PS: If you try to remove the .vmdk's it will fail if there is still a lock present (i.e. it is being used). 

[continuum]

> I recently moved a VM with an RDM attached to another datastore.
A VM used for Veeam should be treated with more caution when you move it.
Unlike other VMs a Veeam  VM can mount and unmount VMs all by itself.
In a regular "normal" VM all vmdks that are not mounted would typically be unused - so a move operation would not copy them.

In a VM used by Veeam that logic probably fails - so you should look into those VMDKs that are left in the original location before you assume they can be deleted.