Skip to main content

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk.vmdk"

It will start to clone the virtual disk in Thick method.

In both disk conversion, should have enough disk space to achieve it since it clones and converts.

Comments

Graham said…
Following a recent customer disaster I had to restore VMs from backup with Backup Exec 2010 that used the VMware Agents using the vStorage API.

VMDK restores were successful, but the VM's failed to start because the VMDK's were thin provisioned when backed up.

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk.vmdk"

...saved my ass. Shame Symantec don't mention that in their best practices...
Anonymous said…
Note that thin provisioned disks change to thick if moved to another datastore when cold migrated as of 4.x. 8 hours of conversions wasted...
Hi,

Would be good to get some info about how to connect to run vmkfstools to complete the guide :)

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires. We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software. This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment. When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console. Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager Creating DSN Create a System DSN f

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only. Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address) ~ # /ipmitool lan set 1 vlan id 333 ~ # /ipmitool lan print1 Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : 255.255.254.0 MAC