Thin provisioning - limited extension of data store

Similar Questions

• Thickness of thin formatting on the same data store?

  Hi all

  is it possible with vCenter to convert thick to thin disc on the same data store format?

  and how?

  Thank you very much

  VMware KB: Change the thick or thin provisioning of a virtual disk

  Please check the useful and accurate.

  Marc

• limitations of the data store

  I have a dell with esxi Server installed. the internal data store is raid 5 totalling 2.4 TBS guidance. The esxi see the 2.4 together and says its available. I was under the impression that it should be 2.0 tb max. This makes 2.4 going to be a problem. I installed it forget the limitation, then remebers. but it seems ok. Please notify.

  Mark

  You will only be able to use 400GO. Reconfigure the table and create disks of 2 or more logical to break to the top of the table.

• How to remove an extension of data store (while keeping the files)?

  Hello world

  I am looking for a way to move/delete an extension of my single data store. My data store consists of 2 extends from ~ 150 GB each. The data on this subject would be inserted in the Go ~ 150 remaining.

  Is this possible? If yes how? ESXi automatically rearrange the data to avoid losing data while dropping an extension?
  
  

  Thank you

  Robert

  It is not possible to remove a measure and keep the original data store.  You must move your data, delete the data store and then re-create.

• VCD 1.5 is not provisioning vms in all data stores

  Hi Experts,

  could someone help me to find why my VCD 1.5 is not put into service of VM in all data stores.

  I have three NFS data warehouses in a VCD and I see that it is not sharing the load between data warehouses. If a volume reached 99% always it is not available on the other Volume that has free space. I heard VCD works on the Round Robin process and also distributes the VM; s in data warehouses.

  Thanks in advance

  Ashok

  With the quick commissioning, we will use the same data store (NFS in your case) that has the existing tree clone linked until you reach the Red threshold of free space.

  Maybe it's not practical with quick commissioning, because once you have 3 GB left... is not a lot of room for the related to grow clones.

  If you want to force the issue, increase the threshold red to something much more on data warehouses.  for example 25% of capacity.

  This will trigger placing of NEW virtual machines on different data stores.

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

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

• Check if the data store supports thin provisioning

  How to find if a data store supports provisioning? Can I assume that no matter what data store that is attached to vmware 4.1 or higher support thin provisioing. Y at - there no flag that I could look up the data of managed objects store?

  There is a property called 'perFileThinProvisioningSupported' in the capablities data store that provides this information

  http://Vijava.sourceforge.NET/vSphereAPIDoc/Ver5/ReferenceGuide/Vim.datastore.capability.html

• Move a virtual machine to a specified data store, creating thin discs

  I apologize for the very basic question.

  Can someone please provlde a working example of a command-line PowerCLI to move a given virtual machine (for example of the ' t "MY VM Sample" with spaces in the name) of a given data store (say, "Source_datastore", I should specify?) to a given data store (say, "Target_datastore") thin discs?

  Concerning

  Marius

  Get - VM "name VM | Move-VM - Datastore (Get-VMHost "HostName" |) Get - Datastore - name of the "DatastoreName") DiskStorageFormat - slim

  You could just specify the data store without having to get the VMhost initially, but if you have multiple clusters with the same name of data warehouses, he can't shoot straight.

• Convert vmdk thin provisioned thick, no risk of lost data on vmdk?

  Dear all,

  I need to figure out if it is possible to inflate a vmdk who was originally also thin stocked but now for some reason, we believe that it must be thick, is it possible now?

  -Turn off the virtual machine

  -Go to the virtual machine folder in the data store, make right click the vmdk and inflate

  -power on the new virtual machine

  Is this necessary? If the machine with two virtual hard drives and they both are thin, can inflate us both during the window of time to stop?

  Please share any possible problems into above account in the light of the case.

  Kind regards

  Just a note: the article contains one sentence which IMO must be formatted in fat and Red:

  There should be no snapshots and the conversion is performed on the basic disk

  Check remove you / commit all active snapshots before trying to inflate basic disks!

  André

• Limited to 2 'task' - Migration of data store

  SAN engineer asked that no more than 2 SVMotions during opening hours.  I have a script to migrate the entire data store, but want to limit 2 SVMotions.

  You can use the parameter - RunAsync and then use the cmdlet Get-task to check how many migrations are "running".

  If less than 2, start a new migration.

  Something along these lines

  $OldDS1 = "OLD_DS01" $NewDS1 = "NEW_DS01" $running = 0
  
   foreach ($OldDS in $OldDS1) {
       $VMs = Get-VM -Datastore $OldDS     foreach ($VM in $VMs)
       {
          $running = Get-Task -Status Running | Measure-Object | select -ExpandProperty Count        while($running -gt 2){
            sleep 5          $running = Get-Task -Status Running | Measure-Object | select -ExpandProperty Count        }
          $VM | Move-VM -Datastore $NewDS1 -DiskStorageFormat Thin     }
  }
  

  If you have other tasks running outside the vMotions in your vCenter, you may need to add a Where clause after the cmdlet Get-task

• Help adding extensions to a VMFS data store

  Hello people,

  I am working on some automation for creation of data store and must be able to add extensions to a data store.  The initial creation of data store works well enough at this point, but I'm a little puzzled about how to add additional extensions.  In my example, I am using the navi cli to make the LUN UID off the coast of the Bay of EMC, then format it correctly for the canonical name the host for the creation of data store.

  I read a little about the extendvmfsdatastore here , but I am not able to separate the part "add the measure" of "questioning the existing data store and remove references to pass."  If someone has an extract whose orders must be performed and the text to pass to the .extendvmfsdatastore method, I'd be very happy.  I know measure in several data stores fall into disgrace with VMware, but I can't migrate 10TB data storage immediately.

  Thanks in advance!

  Brent

  omitted variable section

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

  to connect-viserver $VC - https protocol-$VC_USER the username-password $VC_PASSWORD

  Import-CSV C:\PowerShell\VNX_buildout\TEST-DSCreate\Test_DSCreate.csv | {Foreach}
  $LUN = $_.alu
  Naviseccli-address = $UID $VNX_ADDRESS-User $password-VNX_USER_NAME $VNX_PASSWORD-scope 0 lun-list-l $LUN - uid. out-string
  $UID = $UID. Replace (":", "")
  $POS = $UID. IndexOf("6006")
  $UID = $UID. Remove (0, $pos)
  $CN = $UID. Substring (0.32)
  $CN = "naa. $CN ".
  write-host "CN = $CN - Array MONDAY = $LUN"
  New data store - VMHost $ESX_HOST-name $_ .datastr-path $CN - Vmfs-confirm: $false
  DataSet datastore store-$_.datastr - storageiocontrolenabled $true

  # Add the extensions of vmhbax:C:T:L or naa.xxx or?
  }

  I have reviewed the procedure I used, seems that there is an easier way to do it.

  You can try this version of the script?

  $esxName = "MyEsx"
  $tgtDSName = "MyDS"
  $freeLUN = "naa.6005076801801a34d000000000000078"
  
  $esx = Get-VMHost -Name $esxName
  $dsToBeExtended = Get-Datastore -Name $tgtDSName -VMhost $esx $dsSystem = Get-View $esx.ExtensionData.ConfigManager.DatastoreSystem
  $available = $dsSystem.QueryAvailableDisksForVmfs($dsToBeExtended.ExtensionData.MoRef)
  $lun = $available | where {$_.CanonicalName -eq $freeLUN}
  if($lun){
      $options = $dsSystem.QueryVmfsDatastoreExtendOptions($dsToBeExtended.ExtensionData.MoRef,$lun.DevicePath,$true)
      $dsSystem.extendVmfsDatastore($dsToBeExtended.ExtensionData.MoRef, $options[0].Spec)
  }
  

  If the LUN that you pass the $freeLUN variable is not free, the script will not call the extendVmfsDatastore method

• I have can´t several extensions to my data store

  Hello

  I extend my logic unit number and I have a new analysis on my ESX´s and I can see the new space, but when I try to add a measure (now I have still 4 degrees), West nothing available for the scope. How can it be posible?

  Thank you

  Hello

  Before going further, please do a good backup...

  Yes, I extend my LUN, then I rescan and can see the new size, but I can´t extend my data store to this space...

  That is right. You can't do that if you add a new partition to the first LUN. You can add a partition with fdisk. Once you add the partition, you can then see that partition and add it as a point and formatting in a VMFS.

  Just extending the LUN does not have as much as you cannot extend VMFS without using extensions with VI3. So using "fdisk" in the CLI to create a new partition using the free space. Once you have the partition of type "fb" you can then use vmkfstools to formatting in a VMFS, and then add it as a measure to the existing VMFS.

  If you are not comfortable with vmkfstools or fdisk. Then I would decline the logic unit number once more to its original size if you can remember it EXACTLY, then create a NEW LUN, and adds the new LUN as a measure. If you do not remember the old EXACT size then look at the ALTERNATE.

  ALTERNATIVELY, you can create a new unit number logic of appropriate size and SVMotion/migrate all content for the new LUN of the former then destroy the old ONE. It really is a much less intrusive method.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009, Analyst of DABCC
  ====
  Now available on Rough Cuts: ' VMware vSphere (TM) and Virtual Infrastructure Security: ESX security and virtual environment '
  Also available "VMWare ESX Server in the enterprise"
  SearchVMware Pro| Blue gears. Top virtualization security links| Security Round Table Podcast virtualization

• Block size of a VMFS data store limitations

  I installed my ESXi 5 server with the default block size

  For the moment, I'm trying to convert the Windows Server 2008 and I have the alert message is: "*.vmdk file is larger than the maximum size.
  supported by the data store.

  It is possible to change the size of the block after the installation of ESXI5?

  Please can you help me because I have converter many server and it is not possible to re install my ESXi server.

  Help, please.

  The screenshot I understand you try to make a volume based cloning and you have deselected (i) and selected a share resource (FAT).

  It is possible to deselect the share (in BOLD) resource and give it a try

  Is - this possibe on a disk based cloning an audit?

  Just to be safe, you have enough space on your data store to perform this conversion, and what version of Converter do you use?

• Extension of a data store

  Hello

  I'm trying to expand my existing data store size. I have a HP Proliant DL370 G6 with a Smart Array P410i. I've added 4 additional disks and expanded the chart via HP Array Configuration Utility, so all readers are added at home and in vSphere 4.1 search it shows as having the ability 'new' to 1.9.

  The problem is, when I go in vSphere under Configuration, storage, it shows "total capacity" 833 GB (original capacity when it was created). When I look under the box "Measuring device", it shows the ability of 'new' of 1.91 TB.  (see attached photo)

  If I click on the button 'Increase' it starts the Wizard "Measurement device", but I get nothing that appears in my list and I can't hit next to continue the wizard. I assumed it would be where I can specify the new piece of storage, I added to enlarge the data store but nothing shows, so I'm at a loss. Any thoughts?

  

  Here is a picture of the wizard of the measuring device

  Thank you.

  Welcome to the community,

  increase the VMFS partition on the installation disc is not possible using the GUI. For a description, take a look at http://deinoscloud.wordpress.com/2010/05/03/how-to-increase-the-size-of-a-local-datastore-on-an-esxi4/

  Warning: Make sure you only select the VMFS partition during this operation. In the example it is partition 2, but it could be the 3 with your installation partition!

  Although it should work without problem, I highly recommend you backup the existing VM before doing this.

  André