Thin Provisioning operational entities designated and Donts?

Similar Questions

• 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

• 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

• Thin Provisioning LUNS and virtual disks

  Hi all

  I recently came across a problem with our VMware View environment, where in vCenter about 20 of our virtual office message that there is no more space left. When I looked at the data warehouses that store with my clones related, they have both said more than 200 GB of free space.

  In an attempt to clarify the environment, but do not go off-topic, some of our pools view are configured to give each virtual desktop a disposable disc service end of 4 GB (Temp and swap files). I noticed that in vCenter, the question asked to VMware for more memory space pointed to these disposable disks.

  I was with the support of a few hours... on the side of EMC Clarion, LUN (which are thin provisioned) also showed full... but VMware support was able to create a 1 GB file on the data store that was full according to the Clarion.

  We sent EMC our papers and they were back and just said the table is fine, the LUN was out of space... but this does not explain to me why vSphere showed the LUN as having 200 GB free. EMC said they did not know and I need to talk with VMware. I'm confused, if the LUN was not always full, how we were able to create the 1 GB file on the data store?

  Curiously, all the desktop computers that do not have the disk of 4 GB disposable were very well... they had no problem. I'm almost thinking, perhaps disposable disc was full of temp and file exchange and that where this problem started, but I can't seem to be able to confirm that the 4 GB.

  Another thing is, began to be blocked on this data store, even if these virtual desktops, have been removed from the files. I'm unable to delete records in the data store. I know that I can restart the hosts to unlock, but let's just delete this store of data/lun individual completely.

  I was wondering if anyone has had similar problems or has any advice?

  Mike

  Teas because there are 2 parts of the area of thin provisioning.

  When you create a thin LUN on the side of the table, regardless of the size, it only * affects * about 1 GB (for Clariion).  Like many parts of this LUN if written, it allocates more.

  Now when you create an om VMFS file, unless you use eagerzeroedthick (which you're not), there still, not all these data in a 1 GB (10GB or other) is actually hit or written to the creation time.  Thus, the table side only sees (for example) hit 16 MB.  Now to delete some files on the side of VMFS.  The table does not know that those "affected" blocks are now free (because VMware doesn't have the ability to communicate that back to the table), so it independently as always in use.  As a result, you end up with a shift of how is used according to the table, and the file system.

  So now consider a 500 GB LUN, who think that the painting is "full", but said VMFS has 200 GB of free.  That 200 GB was probably written at a time in its history, then deleted.  Thus, full to the table, but not the file system.  When you create small files, VMFS is overwhelming the space previously used, which the Board considers acceptable, but as soon as you try to use the space that is not be 'recycled', it barfs, because its out of space on the backend.

• New features of Clustering Option VM and Thin Provisioning

  First time post here thank you for patience. I have ESXI 4.1 Essentials Plus, which allows me to have a HA. When I create a new virtual machine he asks me if I want to:

  "Take features of Clustering such as FT.

  This option needs to be checked for HA to work? I want to provision thin, but not at the cost of losing HA.

  No need to enable support for HA FT to work. Also your vSphere edition does not FT.

  Simply select thin provisioned disks and you.

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

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

• Exchange 2010 - is thin provisioned supported or only zeroeager?

  It seems to be conflicting information anywhere on the internet.  When configuring storage for the newspapers and the Exchange databases, disks must always be zeroeager or are provisioed thin discs supported these days in VMWare?  MS say this extension dynamic disks are not supported, but which is under Hyper-V

  See attached PDF.

  Q: are there requirements around storage for my virtualized Exchange solution design?
  A: VMFS on iSCSI and Fibre Channel storage is supported, as are the physical maps and virtual-mode raw device. The use of thin provisioned disks or network - storage devices is not supported by Microsoft for virtualized Exchange deployments.

  Confirmation by Microsoft;

  http://support.Microsoft.com/?kbid=897615

• Thin provisioning / "right-size" database disk

  OK, so I have the setting permissions and ready to deploy to the device.  I don't want to have a 200 + GB DB hard.  I know they say there is a special way, using the OVFTool application if you are using vSphere 4.0.  We run vCenter 4.1 and 4.1 ESXi hosts.  To specify the hard size I want, will it still thinly provision the device with the OVFTool?  I'm looking for clarity in this before deploying the machine, because I will be setting LUN space based on drive of 75 GB database (with room for future growth in LUN).  I apologize if this has already been covered, but I didn't see any other posts related to my question.

  virtualhudak,

  Technically, you should be prevented to deploy the virtual appliance CapacityIQ on a LUN with only 125 GB of free space on the disk.

  You need a data store with at least 258 GB free space on the drive in order to deploy the appliance CapacityIQ. That you complete the deployment wizard, two of the questions asked are if you want the first disk to be configured as a disk, thin or thick. and the same question for the second disk (/ data).

  Once you have deployed the virtual appliance successfully, you can follow the steps to reduce the size of the second (/ data) disk.

  James Ang | VMware engineering
  VMware vCenter operations
  VMware vCenter CapacityIQ
  VMware Capacity Planner
  VMware vCenter Guided Consolidation

• Thin Provisioning

  I'm looking for the pros and cons of the use of provisioning of the disks. In ESX 3.5, there was the problem of the migration of records between data warehouses in which records have been changed from thin in. thick. This I understand has been fixed in ESX 4.0 U1. From what I read, I need to recreate my datstores for Thin Provisioning and then I can migrate live discs from thick to thin. What are some of the gothca otherwise than on commissioning?

  Thank you

  Mike

  Hello.

  What are some of the gothca otherwise than on commissioning?

  For me, the oversupply is the largest.  It creates a thing to have to monitor and take into account during operations.  Creation of alarms is essential, if you follow this path.

  You cannot use them with VMware FT.

  When a thin provisioned disk grows, a SCSI reserve be held.

  The way which drives develop and activities which develop, are also important understand but not necessarily to a witch hunt.  Defragments, copy large files and other normal operations will cause thin disks to grow.  Delete the files from the virtual machine won't give you the back of the space.  The free space can be recovered, but it will take extra work. Some virtual machines just do lend themselves well to it, because of this.  We can expect big savings and not actually bring.

  If performance (including writing intensive apps) are a top concern, so it is better not to use thin discs put in service as well.  You can learn more on this subject in the study of the Performance of VMware vStorage Thin Provisioning.

  Good luck!

• 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

• 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

• Person to contact Toshiba regarding the design and engineering of ideas

  Hello

  I want to contact toshiba to open a company speak with new ideas about the design and operation of laptops.
  I have pictures and images of these ideas.

  Can someone direct me to the right direction?
  Thank you.

  If you prefer please email me directly: [email protected]

  Hello

  First of all, I must say here it s only forum user. You'll be a really lucky guy if someone from Toshiba will be the response to your ad or the means will contact you directly but hope dies last. ;)

  Are you from Europe?
  In any case, I think the best thing is if contact you Toshiba local basis in your country. But the question is if you can contact the guy because normally your interlocutor is a rather authorized Toshiba service provider.

  Of course, you can try it and look for an email address. Maybe you'll find something on Toshiba page in your language. :)