Shrinking VMDK

[Brandon7a]

I have a virtual server running 2003 SP2. The C: drive is 15 GB and the D: drive is 50 GB. I would like to shrink the D: drive down to 30 GB. How would I go about doing this?

Thanks

[Troy_Clavell]

Shrinking, in my opinion, is best done using VMware vCenter Converter

[cainics]

This link should help address your question -

“Your intelligence is measured by those around you; if you spend your days with idiots you seal your own fate.”

[AndreTheGiant]

Also this could be useful:

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[Brandon7a]

I have both Converter Enterprise and the Stand Alone. Which one will work better? I have shrinked the VMDK size before using the converter but this is what I did. I deleted the VM completely off of the VMFS volume. I had a full image backup which I got through VCB and restored the image using Converter back to its VMFS volume. While converting, it gave me the option to resize the disk which I did.

I really don't want to delete the VM and then when restoring it back, resize it.

Is there another way to resize it through converter without having to delete the VM off the volume?

Thanks

[AndreTheGiant]

I have both Converter Enterprise and the Stand Alone. Which one will work better?

Converter Enterprise can convert from ESX to ESX.

Converted Standalone need to be installed on the source VM to convert to a ESX.

Is there another way to resize it through converter without having to delete the VM off the volume?

You can simple rename or remove from inventory.

But converter alway generate a "new" VM.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[Duncan Epping]

I always tell converter that the source is a physical pc and then move it to esx... it's essentially a v2v but you tell converter it's a p2v

Duncan

VMware Communities User Moderator | VCP | VCDX

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[vAdmin]

OK, so the conlussion is using Converter Stand Alone 4.0 client ?

1. Turn off the VM

2. Using vSphere Client / VI Client rename the VM inventory

3. convert the VM into new VM name after the disk space adjustment.

CMIIW

Kind Regards,

AWT

[kjb007]

If you are trying a live migration, or a P2V, the source "server" has to be up and running in order to perform the conversion.

-KjB

VMware vExpert

[Brandon7a]

I will create a test VM today and give that a try. I will let you know how it goes.

Thanks