VM disk thick / thin

Similar Questions

• Find virtual machines with disks of 'thin '.

  Hello

  I'm looking for a script that locates the virtual machines with disks of 'thin' and retrieves information about the provisioned size and "used" actual size and output to a CSV file.

  Thank you in advance!

  This gives you a report on virtual machines with thin discs and the capacity of your hard disk.

  Validated clerk/no values are available only through VM by the data store, I'm afraid, not by the hard drive.

  $report = foreach($vm in Get-VM){    $vm.Harddisks | where {$_.StorageFormat -eq "Thin"} |    Select @{N="VM";E={$vm.Name}},@{N="Harddisk";E={$_.Name}},    @{N="ProvisionedGB";E={[math]::Round($_.CapacityKB/1MB,1)}}}$report | Export-Csv "C:\report.csv" -NoTypeInformation -UseCulture
  

• Convert a disk of thin thickness without interruption

  Can I convert all disks on a thin thickness virtual computer without turning off the virtual machine?

  Yes, if you have the Storage vMotion available in your environment... just migrate the virtual machine to a data to another store and select the disk of destination in. thick.

  Have a look here: http://www.mikelaverick.com/2014/04/back-to-basics-advanced-virtual-machine-administration/

• Conversion of thick disks into thin, but not for any space back

  Hi all

  We have been the conversion of the virtual disks from thick to thin over 30 servers using the method in offline mode, as we don't have storage vmotion:

  vmkfstools-i SERVERNAME.vmdk d thinSERVERNAME.vmdk thin

  The virtual machine is a good mix of NT4 until 2008, vsphere 4.1 all patches installed until 01/05/11. Some we have been recovery of space well when comparing the original vmdk and sizes of vmdk converted file on the console with 'ls s' and 'Browse datastore' in the viclient, but others that we do not get something back into space?

  Using Windows disk defrag to analyze the disks it shows there are no data at the end of the disc also surely the disc should shrink to where the last piece of data on the disk is?

  What you have to do to thin to reclaim any unused space on the virtual FRONT thickness conversion machine drive?

  Once that a disk block was written for her data even if the files have been deleted. You must use something like sdelete before use vmkfstools. Products like sdelete zero free space allowing you to reduce the disk.

• Thick thin disk conversion

  I have a host ESXi 4 with some VMs that I recently migrated on and set to update vmware tools and hardware. I'm doing a migration of thickness for the fine disc, but nothing seems to happen. I use the local disk storage. When I chose to migrate, I keep the same local data store and move to thin frame. The task ends immediately, but when I check the disc in the settings it always shows "thick". I even rebooted, but nothing has changed. Any ideas what I am doing wrong?

  Thank you

  Scott

  ESX is quite smart to know it moves in the same data store, same thing happens when you MOVE a file on your C: drive in Windows to the same folder.

  He actually have to migrate OFF server you and migrate RETURNED as a thin provision...

• How to convert a thickness thin provision

  Hello

  I converted physical machine to virtual .during this process, I chose to files on the hard drive thick delivery.

  now I want to convert all files to provision thin to save storage.how can I convert thick to thin provision.

  I haven't used this link procedure Storage vMotion is much easier, and yes it free your place if you go thin thickness.

  This link may be also useful: http://www.thelowercasew.com/reclaiming-disk-space-with-storage-vmotion-and-thin-provisioning

• How to create a virtual disk thick

  I'm trying to create a thick virtual disk without success. (Do not understand format.)

  I'm using this syntax.

  vmkfstools - ch. 2048 m /vmfs/volumes/myVMFS/rh6.2.vmdk

  I get "error connecting to server https:/localhost/sdk/webservice" maybe etc...

  I suspect that the problem is a lack of understanding of what "myVMFS" is-, but no less - the baffeled.

  Any help very much appreciated. (New for this sort of thing.)

  Ken

  You'll want to add - server filename.vmdk

• How to determine if a disk is thin

  I have a quick query.  I am trying to determine using Powershell, if a disc is thin provisioned or not. Is it possible to programmatically determine? I have been using the following, but it does not provide me with what I want.

  $fileQueryFlags = New-Object VMware.Vim.FileQueryFlags

  $fileQueryFlags.FileType = $true

  $fileQueryFlags.FileSize = $true

  $fileQueryFlags.Modification = $true

  Thank you

  This info is available in the VirtualDiskFlatVer2BackingInfo object in the thinProvisioned property.

  The following script scans through all your virtual machines and all their devices, and the list of disks thin provisioned.

  Get-VM | Get-View | % {
       Write-Host $_.Name
       foreach($dev in $vm.config.hardware.Device){
            if($dev.GetType().Name -eq "VirtualDisk"){
                 if($dev.Backing.ThinProvisioned){
                      Write-Host "`t" $dev.DeviceInfo.Label "ThinProvisioned"
                 }
            }
       }
  }
  

• Confusion of thin or thick disk

  Hi all

  I have a strange problem.

  We have a several s vm disk who told me are thick, but all I can see suggests that they are thin.

  In the data of one of the disks store, it says the following: size and put into service, which shows me the disc is thin.

  

  Do not know why the size shows still as provisioned, while the Linux operating system is no indication that 52 GB is used out of the 100 GB provisioned

  When your right click on the vmdk, you have the ability to inflate the disc, this also highlights the disc being thin provisioned.

  According to my understanding, the inflation option should be grayed out, be they vmdk is supplied thickness.

  When you right-click the virtual machine, select edit it also shows the drive as being thin

  

  Someone has seen a question similar to this one before or can help clarify if my argument of the disk being thin is correct or not.

  Thank you

  JIT

  According to your screenshots, discs are THIN provisioned. If the disk is THICK you get a column 'Provisioned size' (screenshot Ref first). I assume you are using the VI client.

  Also you don't get not "inflate the option" If the disk is THICK. You are right.

  Post edited by: vVision

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

• Change from Thin to thick to help inflate the parameter-> specified is not correct

  Hello

  I wan to convert a VM disk of thin thickness.

  When "inflate" a disk from the data store, I get the message "a specified parameter was not correct."

  What to do to fix this?

  THX

  Please make sure you have machine virtual shutdown and deleted all the snapshot before proceed you to inflate. After you blow up if you see "the disc is not thin-provisioned." This means already changed my thick and in order to see the thickness that you will need to relaod the file vmdk by removing and joining the drive

• Moving-VMThin thin (Thick Powercli to svMotion) feature

  Hello world

  I got this LucD fuction in another post on the forum and changed it to try to convert a large number of virtual machines to thickness thin disks.  I seem to be getting an error on the first virtual machine each time and the second seem to work very well.  If someone could tell what I did wrong, I would be happy.

  Error:

  You can not call a method on a null value expression.
  C:\Users\xxx\Documents\xxx.ps1:33 char: 31
  + $vmView.RelocateVM < < < < ($spec, $null)
  + CategoryInfo: InvalidOperation: (RelocateVM:String)], RuntimeException
  + FullyQualifiedErrorId: InvokeMethodOnNull

  Script:

  $vmarray = @("TestVM1","TestVM2")
  $datastore = get-Datastore. Sort FreeSpaceMB descending
  function {Move-VMThin
  (PARAM
  [Parameter (mandatory is $true, ValueFromPipeline is $true, HelpMessage = "Objects of Virtual Machine migration")]
  [ValidateNotNullOrEmpty()]
  [System.String] $VM
  , [Parameter (mandatory = $true, HelpMessage = "Destination data store")]
  [ValidateNotNullOrEmpty()]
  [System.String] $Datastore
  )
  
  Begin {}
  Necessary to treat #Nothing the
  } #Begin
  
  {In process
  #Prepare migration info, use the .NET API to specify a transformation to thin disk
  $vmView = get-View - ViewType VirtualMachine-filter @{"Name" = "$VM"}
  $dsView = get-View-filter-Datastore-ViewType @{"Name" = "$Datastore"}
  
  #Abort migration if the free space on the destination data store is less than 50 GB
  If (($dsView.info.freespace/1Go) - lt 50) {throw "Move-ThinVM ERROR: data store of Destination less than 50 GB of free space $Datastore."} This script requires at least 50 GB of free space for safety. Please free up some space or use the VMWare Client to perform this Migration"}
  
  #Prepare VM Specificatoin for moving
  $spec = new-Object VMware.Vim.VirtualMachineRelocateSpec
  $spec.datastore = $dsView.MoRef
  $spec.transform = 'rare '.
  
  #Perform migration
  $vmView.RelocateVM ($spec, $null)
  } #Process
  }
  for ($i = 0; $i - lt $vmarray.count; $i ++)
  {
  $datastore
  $snapshot = get-VM-name $vmarray [$i] | Get-Snapshot
  If ($snapshot - eq $null)
  {
  $vmds = get-VM-name $vmarray [$i] | Get-Datastore
  If ($vmds - don't $datastore [0])
  {
  Moving-VMThin - VM $vmarray [$i] - Datastore $datastore [0]
  }
  If ($vmds - eq $datastore [0])
  {
  Moving-VMThin - VM $vmarray [$i] - Datastore $datastore [1]
  }
  }
  If ($snapshot - no $null)
  {
  Write-Host [$i] $vmarray + "has a snapshot" - ForegroundColor Red
  }
  }

  The mystery is solved, the actual name of the virtual machine contained some RegEx metacharacters.

  When they escaped to the oblique, the Get-View filter worked without problem.

  For example, the VM name contains parentheses, which are group of RegEx characters. This

  $vmName = ' TestVM (1).

  Notice-EEG - ViewType VirtualMachine-filter @{"Name" = $vmName}

  won't do anything.

  But

  $vmName = 'TestVM\ (1\).

  Notice-EEG - ViewType VirtualMachine-filter @{"Name" = $vmName}

  will be.

  Tips: Avoid the RegEx meta-characters in the name of your virtual machines.

• Thin VS. thick

  Pessoal,

  Gostaria to hear little but thin in thickness quanto ao e um...

  Ex. Tenho uma VM com 2 don't discos tolls (vmdk) em modo that thin, no cylindrical assim, o Datastore used e um NFS Windows operating system.

  C:\ TAM used 30 = 13 = Go book = 17 GB

  D:\ TAM = 40 used book 14GB = = 25GB

  Na tela vSphere Client, wave mostra os dados do Datastore (figura annex), apreenta o seguinte:

  Put into service = 72,00 GB storage

  No shared storage = 35,58 GB

  Storage used = 35,58 GB

  Finally, I would understand what estes dados are Querenda me say, quando os dados comparo

  that are no OS da VM com mostra o na tela vSphere Client. JA tive outros casos than olhando

  only para has tela vSphere Client a printing that is o Disco tem da VM esta cheio, very

  Quando observado dentro do OS ele esta por exemplo using 50% size.

  Busquei documents talking sober isso, mas will someone wake uma forma but easy (didatica) me

  get works do, Agradea§o desde ja esta como.

  Valeu!

  Fábio Rafael (moussoui)

  Samquejo wrote:

  Hi moussoui

  Thickness mode is a prealloue disk and thin mode is a stretch drive.

  In thick mode, you allways see the same size that provides you with.

  In fine mode, offers you a maximum size and drive grow until this size, but no shrink.

  If you have a thin disk of 10 GB, you can write to 5 GB and the disk drive to catch, but he maintence will sice that size if you format your virtual disk.

  Concerning

  VMTools will decrease the size of the vmdk file...

• Convert a thin disk

  Is it possible to convert a disk of thin to thick in vSphere 4.0

  Hello.

  Open the browser of data store and find the VMDK you want to convert.  Right-click on it and choose the option "Swell".

  Good luck!

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