<div>
Hi securitythreat,<br />
<br />
ESX 3.5 do not have shrink command unlike older version.<br />
<br />
One of the simplest methods to either increase or decrease the size of an existing virtual disk is to use the free VMware Converter utility. When you run the utility it gives you the option to re-size the existing disks so they are either larger or smaller than the original disks. Converter doesn't modify the original disk files; rather it creates a new VM with virtual disks that are the size you specified and copies the data from the original VM to the newly created VM. After you verify that the new VM is working, you can delete the original VM.<br />
<br />
Follow these steps to use VMware Converter to re-size your disks:<br />
<br />
&nbsp; &nbsp; * Download and install Converter on the VM you wish to re-size. Also, you can run Converter remotely if you have the Enterprise version.<br />
<br />
&nbsp; &nbsp; * Select your Source Type, either &quot;Physical machine,&quot; if you are running it directly on the VM or &quot;ESX Server or VirtualCenter virtual machine,&quot; if you are running it remotely.<br />
<br />
&nbsp; &nbsp; * On the Source Login screen select either &quot;This local machine&quot; if you are running it directly on the VM, or your ESX/VC server login if you are running it remotely. In addition select the source VM if you are running it remotely.<br />
<br />
&nbsp; &nbsp; * When the Source Data screen appears it will display all the disks that the VM has assigned to it. Here is where you can resize your disks, choose to select volumes and re-size and then select one of the options, (i.e. 'Type Size in GB') and enter a new size. If you are decreasing the size of the disk you must enter a value larger then the total amount of disk space that is currently in use on the disk. For example if you had 8GB of data on a 24GB disk on your original server, you must enter a value greater then 8GB for the new size.<br />
<br />
<br />
&nbsp; &nbsp; * Next, select a Destination ESX host which will typically be the same host as the source the VM is on. Then assign a name for the VM (name must be different from the source, you can rename it afterwards once you delete the source server), then select a data store to put the VM on, a network for the VM and finally click Finish to begin the process.<br />
<br />
&nbsp; &nbsp; * The time it takes to complete will vary based on how much data is stored on the source server. Once it completes you can power off your source VM, power on the newly created VM and verify that it is working correctly. Afterwards you can delete the original source VM and rename the new VM to match the original name. <br />
<br />
I hope this helps.<br />
<br />

</div>


<div>
Hi,<br />
<br />
I am just following up if this issue is resolved or you need any further assistance on this.<br />
<br />
<br />
<br />

</div>


<div>
<div class="content wysiwyg-content">
In ESX 3.0.2 there was a shrink command that would allow to to take a 100gb volume and divide it into two 50 gig volumes while keeping the data in tact. &nbsp;This was done by using the shrink command. &nbsp;However, this is no longer avaliable in 3.5. &nbsp;Is there a new command for this?
</div>
</div>


In ESX 3.0.2 there was a shrink command that would allow to to take a 100gb volume and divide it into two 50 gig volumes while keeping the data in tact.  This was done by using the shrink command.  However, this is no longer avaliable in 3.5.  Is there a new command for this?

Shrink Command in ESX 3.5

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.