Difference between revisions of "Renaming VM or template storage folder name"

From Notes_Wiki
(Created page with "<yambe:breadcrumb self="Renaming VM or template storage folder name">VMWare vSphere or ESXi|VMWare vSphere or ESXi</yambe:breadcrumb> =Renaming VM or template storage folder n...")
 
m
 
Line 1: Line 1:
<yambe:breadcrumb self="Renaming VM or template storage folder name">VMWare vSphere or ESXi|VMWare vSphere or ESXi</yambe:breadcrumb>
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vSphere or ESXi]] > [[Renaming VM or template storage folder name]]
=Renaming VM or template storage folder name=


It is possible that VM is originally created with some name eg (short-name1).  But later on once it is converted to production, the VM might be renamed to a new name (Eg very-log-name-1).  But if you go to ESXi datastore the name of the folder and various files would still be previous old name used when creating VM.
It is possible that VM is originally created with some name eg (short-name1).  But later on once it is converted to production, the VM might be renamed to a new name (Eg very-log-name-1).  But if you go to ESXi datastore the name of the folder and various files would still be previous old name used when creating VM.
Line 17: Line 16:




<yambe:breadcrumb self="Renaming VM or template storage folder name">VMWare vSphere or ESXi|VMWare vSphere or ESXi</yambe:breadcrumb>
 
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vSphere or ESXi]] > [[Renaming VM or template storage folder name]]

Latest revision as of 08:41, 7 April 2022

Home > VMWare platform > VMWare vSphere or ESXi > Renaming VM or template storage folder name

It is possible that VM is originally created with some name eg (short-name1). But later on once it is converted to production, the VM might be renamed to a new name (Eg very-log-name-1). But if you go to ESXi datastore the name of the folder and various files would still be previous old name used when creating VM.

This can lead to confusion while browsing datastore for advanced operations esp. while try to remove orphan disks (Disks not associated with any configured VM - either on or off).

To solve this there are two options

  • Do storage vMotion of VM to another storage. This will create folder with correct name. After that, if required, we can do another storage vMotion to bring VM back to original storge, this time with storage folder name matching VM name
  • Manually rename files and folders. This is explained in detail at KB at https://kb.vmware.com/s/article/1029513?docid=2094957


Refer:



Home > VMWare platform > VMWare vSphere or ESXi > Renaming VM or template storage folder name