This blog was originally started to better help me understand the technologies in the CCIE R&S blueprint; after completing the R&S track I have decided to transition the blog into a technology blog.
CCIE #29033

This blog will continue to include questions, troubleshooting scenarios, and references to existing and new technologies but will grow to include a variety of different platforms and technologies. Currently I have created over 185 questions/answers in regards to the CCIE R&S track!! Note: answers are in the comment field or within "Read More" section.

You can also follow me on twitter @FE80CC1E


Check out this video using VMWares DPM (Distributed Power Management)

Have you ever had an issue with renaming a vmdk file once the virtual machine has been deployed. What types of tools and/or approaches would you take to resolve this?


Dave Dindia said...

I've run into vmdk renaming issues with VMware. When I rename a VM in vCenter the corresponding files on the VMFS don't change to reflect the new VM name.
For example, if I rename ServerA to ServerB in vCenter all the files on the VMFS will still have the name ServerA.* (.vmdk, .vmx, etc).

There's an easy workaround that doesn't involve manually editing a whole bunch of files but you have to use storage VMotion.

If you have storage VMotion you can migrate the VM files to another datastore which will rename all the files to match the current VM name in vCenter. Then you can just migrate it back to the original datastore.

Hope the info helps.

steve.dibias said...


When i need to rename a server and it's data files i do this:

1. Shutdown vm
2. Rename in VC
3. Cold migrate to another storage/LUN ( take som time for a large server)
4. Power up. ...Done

By doing this everything is renamed ( .vmx , .vmfs , folders ) and the risk of doing something wrong is very little.



Post a Comment