Default MARVIN and Thin Provisioning storage policy

Similar Questions

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

• Followed Thin provisioned "storage used.

  How to follow a thin vm 'storage used?  I can get the storage "provided" by the events, but

  I still have to find the "storage used.

  Did you look at the summary of storage to the virtual machine, which is a new property in vSphere SDK? http://www.VMware.com/support/developer/VC-SDK/visdk400pubs/ReferenceGuide/Vim.VM.summary.StorageSummary.html which provides: (used) clerks and not validated (unused)

  You can also update this information by calling RefreshStorageInfo() before reading the values from a given virtual machine

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  http://Twitter.com/lamw

  If you find this information useful, please give points to "correct" or "useful".

• 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

• 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

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

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

• Thin Provisioning operational entities designated and Donts?

  Hi, im could have some customers who want to configure Vmware Essentials Plus.

  Thin Provisioning seems to be a very good thing and ive used on my test server.  It seems if large in a new configuration I think you want to use a provisioning on all your virtual machines.

  And Yes im aware, I need to keep my eyes on the space and set up some alarms.

  But since im not known enough, I was wondering if there is some designated operational entities and depend on the use of provisioning.

  As it's ok to use Exchange or SQL Server environment.  Or is it correct or not correct to use a provisioning on the operating system or data drive?

  Im hoping its ok to use on everything. Laughing out loud

  My typical clients are customers SMB.  None of them have more than 50 users, so that there would be heavy loads on the servers.

  Typical servers would be 2003/2008 domain controllers, Terminal Server, Exchange 2003/2007 servers and perhaps SQL.  Oh and Small Business Server.

  Thank you

  Mike

  Hello.

  And Yes im aware, I need to keep my eyes on the space and set up some alarms.

  Yes, this is perhaps the most important part of the use of provisioning.

  As it's ok to use Exchange or SQL Server environment.  Or is it correct or not correct to use a provisioning on the operating system or data drive?

  In General, you can use a provisioning for most workloads.  There are a few exceptions (like VMware FT), where it will not be allowed - but that does not apply in most Essentials. The key to whether or not it will be a good fit is to know the characteristics of workloads.  Everything simply because it is SQL or Exchange, does not necessarily it does real work.  When performance counts absolutely, I'd go with a disc of zeroing eager thick.

  Im hoping its ok to use on everything. Laughing out loud

  Learn more about the study of the Performance of VMware vStorage Thin Provisioning for more details.

  Good luck!

• Virtual machines deployed on VSAN without selected with THICK disk storage policy

  Hello

  We had an admin build 50 VMs on our data VSAN store but did not choose the VSAN storage policy while he got the default which allows you to have the THICKNESS of the disks provisioned

  I have chnaged any of the virtual machines to use the VSAN storage policy (which uses a thin) but the virtual machine is still using all the space

  Is there a way to make virtual machines recover white space, now they have a VSAN storage strategy?

  Yes - I have to agree with Duncan. I don't think that there is a way to return/reduce the size.

  An idea is, if you have additional storage, Storage vMotion VM to NFS or VMFS, converting to thin and then back to VSANS with a policy that doesn't have a "thickness".

  Try it with a VM - see if it works.

  A bit of a drag, I know, but I can't think of any other casual way.

  HTH

  Cormac

• 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

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

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

• 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