VMs running on VSAN get renamed

[atoerper]

A few VMs running in a 2-node VSAN cluster have been renamed from their original name to something like this:

/vmfs/volumes/vsan:523c90f268e1b15e-5e743101796223e5/17a67759-e37f-6162-

Is it safe to rename the VM back to the original name? Why would this happen?

[TheBobkin]

Hello atoerper,

Yes it is safe to use RVC to rename them back to their original name:

Login to RVC via your vCenter VM/vCSA Console/SSH and run:

> vsan.fix_renamed_vms <path_to_vms>

e.g. vsan.fix_renamed_vms ./localhost/DCName/Computers/ClusterName/ResourcePools/vms/Misnamed_VM

or to do multiple at once run this with * against the directory listing the VMs:

> vsan.fix_renamed_vms ./localhost/DCName/Computers/ClusterName/ResourcePools/vms/

If the VMs are in specific resource pools then change the where you are running this accordingly.

It will prompt for each VM do you want to rename it (Y/N) and display what the name it will be given as read from .vmx .

More info on this and RVC in general:

www.virten.net/2017/07/vsan-6-6-rvc-guide-part-6-troubleshooting/#vsan-fix_renamed_vms

Bob