Report of thin provision

Similar Questions

• Question about thin provisioned disks

  I did some searching but can't find specific answers, I need and I apologize in advance if these questions are public knowledge. I know also my setup is very small compared to most houses VMWare normally using these forums, but we are moving slowly in the 2nd Decade of the 21st century (or try).

  I have a new install ESXi 5 and move during one ESX3 host that has about a dozen of VMs on it.  I recently built vCenter host servers and my future view connection server.  I'm kind to vCenter again as my previous installation of ESX 3 was a single server and us were not investing in the vCenter at the time option (missed a lot of features and ease of upgrade during this transition, but 20/20 declining).  I'm a little green in using vCenter so take pitty on my ignorance.

  It's more time than I wanted to and I just want to know the best way to change these 2 servers (recently built and configured systems Win 2008 R2) to thin provisioned disks.  I need to keep all the storage space I can and beyond the obvious problem of being able to provide more space than you physically, I have no problem to do so (in addition to get them changed).  If there are negatives I'm missing, please report them to me.  The possiblities that I see are:

  The clone and thin provision then delete the originals.

  Use the stand-alone converter on them (from above).

  Completely rebuild thin provisioned with disks.

  If someone can give me a quick list of possible problems and pitfalls for these opportunities or to get to a better suggestion, please do so and thanks in advance.

  Manual of Clark

  PRIMOS Inc.

  Since you have storage vMotion the clone or standalone VMware converter are both viable options.   Not sure about the disadvantages of these options.

  You didn't say what kind of server it is, but I'm always careful about the cloning of the domain controllers.   Without the option for storage vmotion I rebuild a DC from scratch.

  Post edited by: mittim12

• E thin provisioned ESX

  Buongiorno a tutti.

  Lo scenario:N.2 esx 4.1 e uno equallogic iscsi storage.

  Originally sulle Lun era misconfigured it thin provisioned, ora, by reasons che e meglio no expose, e stato rimosso... my gli esx data it valore dello spazio previous che no coincide con più the realta.

  Just so it could fare by riallineare i valori?

  Grazie

  Corretto. Lo spazio libero reported storage sara sempre dallo minore di quanto reported VMware (my lo stesso problema if ha anche con Linux o Windows collegati directly iSCSI server).

  Andrea

• 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

• Thin provisioning question

  Tonight

  We recently P2V. by 4 Dell servers that all went well.

  When it came to thin provisioning of storage, we encountered a slight impediment. No matter what we do, we cannot recover any space with a provisioning.

  For example, we have only one server, 62 GB C. We have done the following:

  Defragmented

  CHKDSK would be

  SDelete - c (and even z, followed by another - c)

  Then migrate to another store of data configured as thin. We seem to get 0 space back even if Windows reports being 31.6 GB of free disk space.

  Don't get me wrong in the past doing the 4 steps above still retrieved the free space, but just this time on all 4 servers, we cannot recover anything.

  I have even converted to thick, and then to thin in case something to be funny.

  With the help of ESX 4 fully patched on all hosts. The only thing I can think is that when we thin put in service in the past, we were running ESX 4 with no patches and we have recently updated to the current version, but I can't really believe that a fix/update would have broken something as Basic.

  Any idea?

  There is a very simple solution for this problem, I found a couple of weeks ago.

  Do the usual "sdelete - c C:" stuff, and then migrate as Thin put in service in a store of data with a * different blocksize *.

  Then it just works how it has always been.

  It's only when you migrate it to a store of data with the same size block, it's broken.

  --

  Jules

  [email protected]

  www.Jules.FM

• Thin provisioning alert

  Hello
  Is it possible to put an alarm on overuse datastore (Thin Provisioning)?
  Kind regards
  Ronald

  Hello Ronald.
  Space in metric data (Thin Provisioning) store service is not perceived by the current collector agent (I think that you will need to create a custom script agent to recover). Most likely will be available in the new version of the collector agent in the next version of vFogight.
  Concerning

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

• Default MARVIN and Thin Provisioning storage policy

  Hello

  When you use the default storage of MARVIN to vSAN on our new Evo strategy, it seems that all VMs are thick provisioned, not thin.

  My question is, why has it chosen default thick provisioning provisioning method for the storage of MARVIN policy? My understanding of vSAN vanilla is that a provisioning is the default value. I plan to create a new storage for provisioning strategy, but first of all, I would like to understand if thick is preferred on the Evo and, if so, why?

  Thanks in advance.

  It's quite strange - because by default in Evo must be a provisioning is not thick...

  The Evo has to ship to the QEP with the same default values as VSAN. As the team of VSANS, we would recommend thin provisioning...

  Can you confirm that the policy is set to thick. Maybe a screenshot of the policy upgrade...?

  This could be a factory error, or maybe a change not verified by a rogue administrator?

  Can I ask who is the partner of QEP. It may be useful if you send (using posts here) what is Device Evo... (you'll find this under 'health' in the user interface of Evo, next to the health of system - ID is probably something like MAR12345604...

  Kind regards

  Mike

• 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 Provisioning vs thick Provisioning

  Some users say they are not too Committee a disc thin provision.

  But I think that if they are not over - commit then how are they case using the benefits of provisioning. Instead why don't they use thick available?

  You guys agree with my opinion?

  I agree, if there is enough disk space, thin provisioning is basically no benefit to this transfer.

  André

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

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

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