Link to home
Create AccountLog in
Avatar of sglee
sglee

asked on

How to reduce hard disk size in VM in VMWare

User generated imageHi,

  I have a VM on a 4TB Datastore. By mistake, I created VM with 3TB of space and I need to reduce it to 2TB, but I can't.  

  I downloaded vCenter Converter Standalone V5.5.   I can find many links that explains how to do it using vCenter Converter, but I need step by step instructions as to how to use vCenter Converter to reduce the size of hard disk in a VM.
 
  Currently I have two Hosts (Production -192.168.1.2 and Backup - 192.168.1.5). Production host has 500GB space available on the datastore. Both Hosts are controlled by vSphere Client.
Avatar of Billy Roth
Billy Roth
Flag of United States of America image

This may not be ideal, but if the disk is dynamic/thin in vsphere, you could simply shrink the partition in the vm client to 2TB using disk manager, and it would never use more than that.
Okay, if you want to use "VMware Converter 5.5" the first you need to do, is install on the VM to be converted, to create a V2V.

My EE Article contains videos, I've created for EE Members

HOW TO:  P2V, V2V for FREE - VMware vCenter Converter Standalone 5.5

HOW TO: FAQ VMware P2V Troubleshooting

let me know when done.

or you can use this article

HOW TO: Shrink a VMware Virtual Machine Disk (VMDK) in 15 minutes
Avatar of sglee
sglee

ASKER

Andy,
 
 Can you give me step by step instructions as to how to do this instead of links please?
1. Install "VMware Converter 5.5" on the VM to be converted, to create a V2V.

Post back, when done.
Avatar of sglee

ASKER

Installed and looking at VMWare vCenter Converter Standalone window.
Avatar of sglee

ASKER

W2008 Std 64bit.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of sglee

ASKER

I followed up to Step 20 and it started copying now.
This process essentially is "Clone" or "Migrate" with hard disk re-size option.
It's actually a Disk Clone with Re-Configure. (which includes, disk/partition alteration)
Avatar of sglee

ASKER

User generated imageAfter successful copy to production host, I turned off the original VM in backup host and turned on the VM "Backup1" and I got this error.
I checked the CDROM and it was empty, so I assigned W2008 64bit ISO file.
But I still get this error.

If this is due to a hardware change, should I migrate this back to the backup Host now the hard drive size has been adjusted?
Avatar of sglee

ASKER

I am re-doing it and this time, I am using staying with same HOST and DATASTORE.
Let's see how it works.
Avatar of sglee

ASKER

It worked. So I should have stayed within the same host and datastore.
One problem that I noticed is that I need to activate the OS again.
When I moved the VM from one host to another, I did not have to.
But when you go thru a conversion which is essentially creating a duplicate VM, it make sense that the system will require activation again.
datastore and host changed should not cause any issues.

Conversion can cause RE-Activation, because the machine is being converted, and disk serial number has probably changed.
Avatar of sglee

ASKER

User generated image"datastore and host changed should not cause any issues." -->
If that is the case then, perhaps first time when I tried, I took default settings which are both checkboxes checked for (1) Ignore page file and hibernation file  (2) Create optimized partition layout.
But 2nd time, I unchecked them as seen above.
I followed the very same instructions here, because I noted those instructions, as I did it, and had no issues with the V2V I created.
Avatar of sglee

ASKER

User generated imageUser generated imageAndy,
  This V2V is successful, but it comes with one problem: having to activate the OS again.
  You also have an article "HOW TO: Shrink a VMware Virtual Machine Disk (VMDK) in 15 minutes".
  As you see in the screenshots above, I allocated 3TB into this VM by mistake and since I can't create a partition no bigger than 2TB, 1GB is being wasted and that is the reason I wanted to shrink the hard disk space (3TB) that I assigned to this VM.

  Having said that, if I follow your article "HOW TO: Shrink a VMware Virtual Machine Disk (VMDK) in 15 minutes", would I be able to free up that 1TB being not recognized by Windows OS?
By nature of conversion, it's likely to cause a re-activation. Because you are really creating a "new computer".

Yes, if you chop off the 1TB not being used by Windows, it will be available to the datastore again.

follow my EE Article.

HOW TO: Shrink a VMware Virtual Machine Disk (VMDK) in 15 minutes
Avatar of sglee

ASKER

I have decided to simply erase the VM and re-create a new VM with 2TB partition.
Thank you for your help.