Recovery of space on thin provisioning vmdk

Similar Questions

• 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.)

• 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.

• Thin-provisioned VMDK & vSphere Client?

  Hi people,

  Just a quick, I have a VM thinly provisioned created on a host of test ESXi 4U1; I connect directly to the host via vSphere Client.

  When I download the file of the virtual computer on my own machine using the browser to store data, the end result is a flat file on my machine...  What is everything?  If I have a thin 60 GB disk implemented with only 12 GB allocated and want to take a copy, it ends up as a flat file of 60 GB transfer and waste all that space on my machine...

  Am I missing something obvious here?

  Thank you

  Alistair

  Hello

  the thin supply function is available only on a VMFS and some NFS data stores.

  When you copy a virtual machine on your pc, it does not matter if the VM vdisk is thick (flat) or thin, on your pc always it is thick (flat).

  Then, the slim advantage is only on the data store, not when you copy/transfer of the virtual machine on your pc.

  For example, it does not happen on vmware server 2 or workstation because the virtual machine is placed (previously assigned or not) in the files of the operating system.

  Hope this helps

  Best wishes / Saludos.

  Pablo

  Please consider to assign all useful or correct answer. Thank you!! - Por favor considered premiar any respuesta correcta o util. ¡¡MUCHAS gracias!

  Virtually noob blog

• 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.

• 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

• 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.

• 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é

• Thin Provisioning does not work or unable to find space?

  Hello

  I have about 30 virtual machines using thin provisioning format. I found 1 especially with a 20 GB drive, TYPE THIN and 19.9 GB used. I entered in the console, check use of space inside the linux and it has 90% free. It uses only 2 GB.

  My question is why not taking advantage of the thin provisiong as other virtual machines. Any ideas?

  Post edited by: vmroyale to remove the PLUGS all THE of the subject line

  Fill the empty space with zero and do svmotion with thin disk as target, it should reclaim the unused space.

  It's how recover you for example 10 gigabytes of Linux root fs

  DD if = / dev/zero/foo bs = 10240 count = 1 M

  RM foo

  then svmotion

  Tomi

  http://v-reality.info

• 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

• Backup errors with backup of thin provisioned disks on ESXi 5.1

  Hello

  I try to set up a backup solution for two servers in ESXi 5.1. (free version).

  I have installed and configured the ghettoVCB successfully and everything seems to be ok.

  However, when I start to create a backup, the process would end with an error :-(

  It didn't matter if the server is enabled or disabled, I get the same result.

  All data warehouses are local, 2 x free WD500GB with plenty of space.

  There is no snapshot, anything that could (in my eyes) prevent a good backup.

  The server works perfectly, when turned on.

  I'd appreciate any useful comment. Thanks in advance! The log is attached.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #./ghettoVCB.sh f vms_to_backup
  Recording output to ' / tmp/ghettoVCB-2013-05-25_20-56-28-324192.log '...
  2013-05-25 20:56:29 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2013-05-25 20:56:29 - info: CONFIG - VERSION = 2013_01_11_0
  2013-05-25 20:56:29 - info: CONFIG - GHETTOVCB_PID = 324192
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_VOLUME/vmfs/volumes/backup/ghettoBackups =
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 3
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2013-05-25_20-56-28
  2013-05-25 20:56:29 - info: CONFIG - DISK_BACKUP_FORMAT = thin
  2013-05-25 20:56:29 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2013-05-25 20:56:29 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
  2013-05-25 20:56:29 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2013-05-25 20:56:29 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2013-05-25 20:56:29 - info: CONFIG - LOG_LEVEL = info
  2013-05-25 20:56:29 - info: CONFIG - BACKUP_LOG_OUTPUT = /tmp/ghettoVCB-2013-05-25_20-56-28-324192.log
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_COMPRESSION = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
  2013-05-25 20:56:29 - info: CONFIG - ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 0
  2013-05-25 20:56:29 - info: CONFIG - VMDK_FILES_TO_BACKUP = all
  2013-05-25 20:56:29 - info: CONFIG - VM_SHUTDOWN_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - VM_STARTUP_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - EMAIL_LOG = 0
  2013-05-25 20:56:29 - info:
  2013-05-25 20:56:35 - info: start the backup for server W2003
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk'...
  Clone: 36% of fact.
  2013-05-25 20:59:34 - info: ERROR: error in the backup of "/ vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk ' to W2003 Server
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard '...
  Clone: 66% of fact.
  2013-05-25 21:08:59 - info: ERROR: error in the backup of "/ vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard" to W2003 Server
  2013-05-25 21:08:59 - Info: backup time: 12,40 Minutes
  2013-05-25 21:08:59 - info: ERROR: impossible to W2003 server from backup because of the error in VMDK backup!

  2013-05-25 21:09 - info: # final status: ERROR: No. VMs saved! ######

  2013-05-25 21:09 - info: = ghettoVCB JOURNAL END =.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #.

  > However, when I start to create a backup, the process would end with an error :-(

  This is not correct.  Depending on your position, you've got to 66%, until he ended with an error.

  I have the same problem. In my case, I make a virtual disk full and mount it with Server 2003 for project a NFS volume.  I use GhettoVCB, as you do.  It uses the standard vkmfstools in the script to make the clone/backup.  I have proven that the problem also occurs when you use the command line vkmfstools.  GhettoVCB has the bad habit of you cache the error code.  The error code is he ran out of disk space, which we both did not happen.  Once the problem occurs, the only way I could fix is to delete the virtual disk and start over, however, the problem will come back.  The problem didn't surface until what I moved to ESXi 4.0 5.1 on the servers.  Through this process, the hardware off the VMS version did not change, nor dare, because I may need to take 5.1 and back to 4.x.

• Thin provision security issues

  Hello

  I remember said that if you thin provisioned a disk and then used a file recovery tool it may be possible to read data from the underlying storage system.

  I just did a quick google but I couldn't find anything,

  It is never true. The documentation that I can find for v5 says that a disc thin provisioend returns 0 if it has not already been written in.

  Thank you

  Jeremy

  The feature "fake zero" is what protects against that and as far as I know, is true since ESX thin VMDK support.

• Ability to store data when thin provisioned

  Hi all

  VSphere 4.1 running in a cluster of two hosts, this cluster uses a Dell Equalogic PS4000 SAN for storage.

  Confusion I have is with thin configured data stores and my Exchange Server (2010) - running on MS Server 2008 R2 Ent.

  Exchange server uses three data warehouses on the San, one for the OS, one for data and one for newspapers.

  The data of databases store is the one that gives me problems, it has been defined as thin provisioned 750 GB, when I look on the SAN & via VCenter he said 90% full until she went to 100% after the SAN sent several alerts - the virtual machine then crashed with out-of-space error.

  To cut a long story short, I have twol questions

  (1) in this case why the SAN & VMWare say the data store is full, BUT when I connect to the virtual Windows computer it was about 50% in use?

  (2) when the data store that contains the databases filled I don't understand Exchange has fallen more but why why the crash of the VM?  The OS data store still had plenty of free space.

  I got this error by increasing the space of 100 GB to 850 GB data store while the virtual machine is very well (even if Windows was complaining to a stop suddenly unexpected).

  Thanks in advance for your help.

  K

  And without perspective, as it was put in service end and touch 750 GB, 300 GB, then was removed, it would not 750Go because it may not decrease in size - is that correct?

  (This would answer why the SAN says he uses 750Go of 750 GB, but Windows thinks there ish 300 GB free).

  Yes, that's correct... the recovery of unused/dead/removed space don't is not automatically made.

• thin provisioning considerations

  We are currently evaluating using fine provisionig in a full server environment (not customers/VDI)

  are there warnings and best practices?

  I mean:

  a provisioning induced fragmentation and degradation of performance on the vmfs datastore?

  What happens when a data store is overcommitted and a virtual machine tries to allocate more storage? the virtual machine stop suddenly?

  Hello.

  are there warnings and best practices?

  The largest practices and warning the two is to have additional monitoring to make sure that you do not run out of space.  vCenter that is out of the box, but make sure that it is set up to your liking.

  Other warnings:

  Race defragments will cause thin discs (s) to develop at varying degrees.

  Cannot be used for FT enabled VMs in vSphere.

  a provisioning induced fragmentation and degradation of performance on the vmfs datastore?

  Fragmentation is not a problem.  For write intensive workloads, there is a performance impact.  Learn more about the performance in the study of the Performance of VMware vStorage Thin Provisioning.

  What happens when a data store is overcommitted and a virtual machine tries to allocate more storage? the virtual machine stop suddenly?

  More about that in "[Easy recovery of a data store full VMware ESX | ]. "[http://www.vcritical.com/2009/10/Easy-Recovery-from-a-full-VMware-ESX-datastore/]" on the site of Eric Gray.

  Good luck!