Thin-provisioned VMDK & vSphere Client?

Similar Questions

• Thin provisioned VMDK consume all available space

  Hello

  • Server: Win 2008 R2 with SP1 (file server)
  • Storage: VMDK on VMFS5 datastore (thin provisioned), which underlies the SAN fiber storage
  • vSphere: vCenter Server Standard 5, ESXi 5.0 Patch 2 (build 515841)

  ... So, I have a VM file server running Windows 2008 R2 with SP1.  The system (c) partition has been successfully thin (VMDK using 13 GB to 40 GB).

  However, for all subsequent hard disks virtual created on the server, the NTFS partition is very slow to get into shape - and the actual size of the VMDK creeps slowly up to the size of the VHD (you can see the gradual rise of the VMDK size in the browser to store data during the formatting process).

  The VMFS data store that we create new virtual hard disks is version 5.  All virtual machines with virtual hard disks on VMFS version 3 seem to be supplied thin OK.

  Nobody knows what could happen here?

  Hello

  Do you use quick format?

  Otherwise, your score will take up any space. Check here:VMware KB: using thin provisioned disks with virtual machines

  "If a guest operating system needs to use a virtual disk, the must invited first operating system partition and format the drive in a file system it can recognize." Depending on the format selected in the guest operating system, the format can cause the disc thin provisioned in full size.

  For example, if you have a drive end with a Microsoft Windows operating system implemented and format the drive, unless you explicitly choose to fast formatting, Microsoft Windows format tool written information to all sectors on the disk, which in turn inflates the disc thin provisioned in full size. "

  Kind regards

  Julien.

• Shrink a thin provisioned VMDK

  I have a VMDK thin provisioned is 500 GB. The real Windows Partition is only 150 GB. I would change the VMDK disk 150 GB thick put into service. What is the best way for me to go on this?

  If you prefer GUI, then use the converter otherwise vmkfstools is a powerful CLI command.

• Recovery of space on thin provisioning vmdk

  Hello

  I've been running sdelete x:\ - c and vmdk migration between different LUN but have not managed to regain space lost in return.  I also tried the-i disk.vmdk d vmkfstools command thin newdisk.vmdk within the console and still have no luck with it.  Is there a more effective way of zeroing on the unused sapce rather the 2 methods mentioned?

  Thank you.

  Sounds like it may be the cause of FS3DM that is described here: http://kb.vmware.com/kb/2004155

  Although the KB's 4.x looks like he can still exist in v5.x from the comments here: http://www.yellow-bricks.com/2011/02/18/blocksize-impact/

  / Rubeck

• How to reduce the size allocated to a thin provisioned VMDK

  I want to reduce the amount of space allocated to a Windows Server 2008 VM 400 GB to 250 GB. Already, I have used SVmotion to free up space and shrunk the drive in Windows. Now, however, I need to reduce what amounts to her I can avoid too assigned (test boxes tend to actually fill their disks with backup files, and since they are overallocated, we're crashing servers). Simply, I don't know how to perform the task without losing any data and really appreciate anyone's help.

  The converter will be responsible to make happy, to grossly oversimplify it Windows.

  The network card will change, and the server will get a new MAC address and must be re - IP addressed as well. Other than the process is fairly simple and Windows don't miss anything. The real beauty of it is that you have the source still available VM, so if something goes wrong there is an instantaneous failover.

• Is it possible to migrate a virtual machine to thin provisioned disk?

  I have about 100 VM in a resource pool dedicated to called "Archive"... Well, archiving.  These virtual machines are currently powered off but every now and then we will get pulled for a developer to work on (they are for the most part, the virtual computer with client customizations if they are changed about once a year).  I'm quickly running out of space on this SAN but all discs are thick provisioned and using the disc is maybe 20-30% on average.  Also, I want to move them to a new large store of data I created for them.

  Of course, I choose Migrate & gt; Change store data & gt; Thin provision in vSphere Format and I'm done.  However, it would be nice to not do this 100 times.

  Move-VM does not seem to be capable of this, and I have not been able to find a workaround.  Is there a way to convert the thin and then perhaps Move-VM? Or I'll just on this all wrong.

  Thank you!

  You can try this script?

  He's moving vms to data store 'EMCSAN:Datastore01' trying to change the format of storage for Thin

  $dsView = Get-Datastore -Name "EMCSAN:Datastore01" | Get-View -Property Name
  
  Get-VM  | % {
  $vmView = $_ | Get-View -Property Name
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec
  $spec.datastore =  $dsView.MoRef
  $spec.transform = "sparse"
  
  $vmView.RelocateVM($spec, $null)
  }
  

  / Yasen

• How to recover free space on Thin provisioned VM

  Hello

  We are trying to recover the thin provisioned VMDK using below UNMAP commands on esxi5.5 update1 host but get error backup volume not supported for UNMAP and we can see that delete also not taken in charge and all status by checking the ATAS list his indicates that the plugin is not loaded we use IBM SVC (VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  Let know us how to load the VMW_SATP_SVC plugin to the ESXi 5.5 update1 host and also suggest how to recover free space on thin provisioned VMs

  Here's the output of command, we checked and we suggest to conduct thorough on this

  **************************************************************************************************

  ~ # esxcli storage vmfs unmap-l NONPROD-DS01

  Backup volume 5390312 a-1f3a16fd-b578-5ef3fc1eb0bb devices do not support undo the MAPPING

  *************************************************************************************************

  *******************************************************************************************************

  ~ # esxcli central storage peripheral vaai situation get naa.60050768018105ced80000000 d

  CF 00010

  1. NAA.60050768018105ced8000000000010fc

  VAAI Plugin name:

  ATS status: supported

  Clone status: supported

  Zero status: supported

  Delete status: unsupported

  ********************************************************************************************************

  ********************************************************************************************************

  ~ # esxcli storage nmp ATAS list

  Description of default name PSP

  -------------------  -------------  --------------------------------------------                                                -----------

  Tables VMW_SATP_ALUA VMW_PSP_MRU nonspecific media that use the Protocol AL AU

  VMW_SATP_MSA VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_DEFAULT_AP VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EQL VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_INV VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EVA VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_ALUA_CX VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_SYMM VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_CX VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_LSI VMW_PSP_MRU placeholder (not loaded plugin)

  Non-specific bays of VMW_SATP_DEFAULT_AA VMW_PSP_FIXED Supports active/active

  VMW_SATP_LOCAL VMW_PSP_FIXED direct support of connected devices

  ************************************************************************************************************************

  Hi friend

  I checked with the storage provider and they confirmed that the storage system (currently no products support midsize or SVC SCSI unmap commands used by space VAAI claim.)

• ESXI 5.1 "the disc is not thin-provisioned" after copying to the new data store vmdk

  I wanted to create an external backup as a 2nd VM ready-to-run on the 2nd data store.

  I've removed all snapshots, stop the machine virtual and exported the OVF file to a computer, adjusted to the size of the original virtual machine starts in Gparted to update the partition and restart. All very well.

  I then tried to deploy the OVF in the data store alternative (235GB slim, thickness according to the deployment of 250 Wizard). I tried both thick and thin but the error message "cannot deploy the OVF. The operation was cancelled by the user.

  I then manually downloaded the VMDK & OVF file to the 2nd data store and tried to inflate but then received the message "a specified parameter was not correct. The disc isn't thin provisioned. ».

  It seems I have dealing with the same thing, as this is the document here (http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3-release-notes.html).  However, I have no idea what to do now... and I'm worried because it seems that my backup plan may not work if I can't restore an OVF/VMDK from a disk of visas.

  The solution to the first problem here: https://communities.vmware.com/message/2172950#2172950 that solved my problem 2nd too.

• Thin Provisioning - SAN or VMDK layer

  Hello

  With the option to set up a thin disk with vSphere or the SAN layer, which is the best?  Is it possible the provision at the level of the SAN and VMDK or could eventually create confusion.  I guess that SAN provisioning would offer better performance too?

  See you soon

  gogogo5

  Very detailed information on this subject available on the blog of Chad from EMC here: http://virtualgeek.typepad.com/virtual_geek/2009/04/thin-on-thin-where-should-you-do-thin-provisioning-vsphere-40-or-array-level.html

  Kind regards

  Hany Michael

  HyperViZor.com | Virtualization and all around him

• Thin provision NFS works only for instant VMDK

  Hi guys,.

  We have a host of ESXi 4.1 using NFS as a storage device. NFS is provided by the platform, Bluearc Mercury.

  Whenever I create a new virtual machine, for Thin Provisioning option is checked but also gray outside. There is a line saying:

  "Actual allocation policy will be determined by the NFS server.

  I'll check the newly created VMDK and it's a thick disk, it consumes as much disk space I put for the disc size.

  So, it makes me believe that the Bluearc Mercury does not support provisioning.

  The strange thing happens after that I did a snapshot, another VMDK as server - 0001.vmdk was created, and it's the thin disk.

  Someone at - it the similar problem?

  Kind regards

  Derrick

  Showmanlkz,

  On the BlueArc server, file systems are provisioned files, thin as VMDK files are created as "fragmented files".  Just a slight difference in terminology, but the effect is what you're looking for in what concerns the commissioning only the disk blocks that are actually used (thin provisioning).

  If you have created a 10 GB VMDK file, but have only 5 GB of data on the inside, only pointers to these 5 GB of data blocks will be created.  Us will not pointers to blocks of empty data.  Standard orders will make reference to the metadata VMDK structure and will report on the 10 GB file.  In order for a command 'df' to show the use of real drive (5 GB), rather than the allocated size (10 GB), you must enable the "true fragmented file" mode.  Contact the BlueArc TAC for the real run command.

  Snapshots are a completely different beast.  By default, they are only pointers to a point static instant copy.  However, if you use our new feature JetClone to create clones in entry level file, these files will be also thin provisioned, only as the clone diverges in content data from the original VM has been created between more and more.

  Julie HG

  Product Manager, BlueArc

• VMware ESX 4.0 Update 1 with HP LeftHand P4500 Thin Provisioning (SAN based and client based?)

  I know with ESX 4.0 that you now have the option to select a provisioning on the side of ESX.  I'm already thin provisioning my LUN on the left side.  I do both or just the side SAN?  Also, I heard some people say that it is better to use a block size of 8MB for best peformance of SAN, do you think it is recommended/best practices as well?  Thanks in advance.

  The point to offer 8 MB block sizes is flexibility.  Because you cannot change the size of the block without reformatting the VMFS file system, you probably don't want to need to.  There is a great overview of a few points on this theme to the yellowwire from bricks.  I recommend you start here and follow the links.  It only takes 5-10 minutes, and you will be able to make your own choices.  For us, we're all migrate to blocks of 8 MB.

  What about thin provisioning, I have no practical experience.  But here's my point: If you sell thin anywhere, you have a more complicated system to follow in terms of space put into service and space required.  Must be taken account of this that data may coming in the future, or you might run out of space.  So, I ask you where you want to configure the monitoring of the use of space and how you want to administer the storage.  If you want to do on the primary server, and then stick with that.  If you want your VMware administrators to manage management, then do it in VMware.

  My recommendation: If you're already doing it on the back-end successfully, then stick with what you have.  Whatever it is, do it only in one place.  Otherwise, you're probably too complicate your configuration.

  Virtualization of happy!

  JP

  Please consider awarding points to useful or appropriate responses.

• Thin Provisioning not reduce size of backup

  I use ghettoVCB to save some of my virtual machines. I changed some of these virtual machines to use a provisioning in an attempt to reduce the size of backup. When I browse my store of data using vSphere Client, I see that the thin provisioned disks take less space. However, when I go back to a NFS store on a Windows Server 2008 R2, backup sizes are the same as they were when I used thick provisioning. Is this normal on a Windows NFS share? I did specify a provisioning for ghettoVCB.

  I ran sdelete and VMWare Converter to try to reduce the disks; This decreases the size of the disk that I see in the browser to store data, but the size of the backups on the NFS share was always the same.

  I don't have access to an NFS server ATM, but tests on a ZFS volume w/de-dupe that is exported outside like NFS, I can confirm that on the host ESX virtual machine appears as thin provisioned and when you do ls - lha on the VMDK is 8 GB and not 0 GB, but when you look at the free data store no space has been consumed during the creation of this new virtual machine. It all depends on your server and it is the configuration of NFS, I agree with RParker, you'll want to enable deduplication on your NFS server if it is supported. Put into operation end is handled differently on the NFS Server vs on VMFS volume and it dictated by the server NFS itself on how it is configured to manage a provisioning.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• Thin Provisioning does not not as expected

  In my esxi 4.0 test environment, I created a machine thin-provision xp-32 bit.

  Provisioning was assigned to 50 GB and is a minimal install of XP (just the operating system, patches, vmware tools) leaving 44.7 GB free.

  The flat file hower, looks like she is supplied thickness.

  I searched every thread here and see no similar problem.

  Am I missing something? I thought that the vmdk file should be around 5 GB to do, 50...

  I do not use vcenter, just download free esxi 4.0.

  

  / vmfs/volumes/4afd5954-40f87539-4DE3-001aa0a6e9a3/XP pro SP3-Virgin # ls - al

  drwxr-xr-x 1 root root 1400 19 Nov 12:40.

  drwxr-xr-t 1 root root 2240 19 Nov 12:14...

  -rw - 1 root root 53687091200 Nov 12:40 19 XP Pro SP3-Virgin - flat hard

  -rw - 1 root root 8684 19 Nov 12:40 XP Pro SP3 - Pristine.nvram

  -rw - 1 root root 506 18 Nov 17:55 XP Pro SP3 - Pristine.vmdk

  -rw - 1 root root 0 18 Nov 14:00 XP Pro SP3 - Pristine.vmsd

  -rwxr-xr-x 1 root root 2731 19 Nov 12:40 XP Pro SP3 - Pristine.vmx

  -rw - 1 root root 1866 18 Nov 17:55 XP Pro SP3 - Pristine.vmxf

  -rw - rr 1 root root 230154 19 Nov 12:13 1.log - vmware

  -rw - rr 1 root root 63177 19 Nov 12:40 vmware.log

  Hello hamm3r,.

  It is normal that you feel. A directory of the regular list will show 50 GB. You need to do a query (use of the drive/directory) with the following:

  -ah *.

  Which should show the actual size of the vmdk file. You can also watch free space of your data store in the VI client to check that it lines up with your expectations. I hope this helps.

  Don't forget to mark this "correct" answer or 'useful', if you found it useful (you'll also points).

  Kind regards

  Harley stagnate

• New-VM cmdlet always deploys "Thin-provisioned" VMs - need help

  Hi all

  I am at a total loss on this and spent several days trying to figure out what's wrong.  I'm deploying a new virtual machine from a template using PowerCLI version 5.1 Release 1.  The model is thin-set as all our models are, but when you specify my "New - VM" command, the resulting virtual machine always deploys as thin-provisioned even if I specify "thick".  Here is the command I use:

  PowerCLI C:\ > New-VM-model $templatename - $datastoreClustername - DiskStorageFormat EagerZeroedThick - $hostname - VMHost Datastore name $newVMname - location $foldername

  The above command returns the following error that 'EagerZeroedThick' is not a valid for the parameter - DiskStorageFormat option (although I see it clearly is done by "Get-Help-detailed New - VM")...:

  New - VM: 20/02/2014 12:09:18 new - the specified invalid VM storage format. Valid values are "Thin" and "thick".

  Online: 1 character: 7

  + New-VM < < < <-Template (model Get - Id VirtualMachine - vm - 1060) Datastore - Orion1_DSCluster - DiskStorageFormat EagerZeroe

  dThick - VMHost orion2esx01.cisco.com - name rcdn6-vm91-8-location "generic user (jstest).

  + CategoryInfo: InvalidArgument: (:)) [new-VM], InvalidArgument)

  + FullyQualifiedErrorId: Client20_VMServiceImpl_GetnerateCloneSpec_IvalidStorageFormat, VMware.VimAutomation.ViCore.Cmd

  lets.Commands.NewVM

  So I try the same command above, but this time by using 'thick ':

  PowerCLI C:\ > New-VM-model $templatename Datastore thick - VMHost $hostname - DiskStorageFormat - $datastoreClustername - name $newVMname - location $foldername

  The above command will successfully deploy a new virtual machine to the specified model, but the resulting virtual machine will always be Approvisionnés Thin rather than thick as I said...

  I have Google had the devil on this issue and did not happen to something that helps me...  I tried all the combinations of parameters, and the parameter order hoping that would be the thing without result.  As I said, I am at a complete loss and hope someone here can point me in the right direction.

  Sum, my 2 questions are:

  1. Why is EagerZeroedThick not considered as a valid option for the setting -DiskStorageFormat even if "Get-Help-detailed New - VM" clearly states that it is?  (I've seen a lot of example online of people using this option as well)
  2. Why the new virtual machine being deployed as a thin-put in service of the virtual machine, even if I specify thick for the setting -DiskStorageFormat of New - VM?

  It is a 1 vCenter/vSphere 5.1 update environment.

  Thanks in advance for your help.

  I finally received a response from the Vmware Support on this topic and thought I'd share it for anyone else running in this issue:

  VMware support:

  "I confirmed and discovered that it is a bug that is already running of our public relations team that suits him.

  And confirmed that this will be fixed in the next major release of VMware CLI power.

  And now, there is no ETA for it but I think would it as well as ESXi 5.5 U1 version but I can't confirm it. »

• Save space on the disc thin provision

  Hello.

  I have a virtual machine that has thin provisioned N. 3 disks:

  • 1-> provisioned size 20 GB
  • 2nd-> size 3 GB provisioned
  • 3-> provisioned size 20 GB

  If I look on the use of the storage on the server ESXi 5 (VI client) I see this:

  

  But if I connect on the virtual computer, I see this:

  

  With a simple calculation, I don't see that really used on the virtual machine storage size is only (20 - 8,64) + (3-0, 746) + (20 - 5,46) = 28,15 GB.

  Very different 40,48 GB storage used .

  The question is:

  is it possible to reclaim unused storage space?

  In other words: is it possible to align the "storage used" showed on the resources of the ESXi server to that actually used from the VM?

  Thanks in advance.

  You can use vmkfstools with the option ofpunchzero to recover the disk space of the thin configured virtual disks. To do this, you must first set to zero unused space within the OS itself invited, then turn off the virtual machine and run the vmkfstools command.

  André