Thick thin disk conversion

Similar Questions

• SVmotion - thick disk of source-> svmotion-> should become a thin disk in vSphere CLI power

  Hello

  I tried to perform a SVmotion using vSphere CLI power and it works fine.

  But when executing the SVmotion, I also want to mention the DISC FORMAT' i.e. ' thin... ". While the SVmotion I want the drive to be THIN DISK PROVIDED.

  Move-VM - VM (VM-Get-name litbuildvm) - Datastore & lt; name of store data & gt;

  Can someone help him, now in the above command, the source vmdk is THICK implemented after SVmotion remains thick.

  But I want to make the disk vmdk source which is THICK to THIN after SVmotion in vSphere CLI...

  Help, please

  Deepak

  Yes, that's correct.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Are thin disks for the readers of the OS 'Enterprise Ready'?

  I thought a lot about post of Leo on recommended model VM for a while now, but I'm still worried... or rather... I am still ignorant of things?  :|

  Specifically, I wonder how wise it is to use thin discs for our environment. A brief history... We are currently using EMC Clariion CX storage for all of our warehouses of virtualization. We have already built just to the South of 300 production and development of virtual machines in our environment with C: readers built on thick records. We are not currently using VCB in our environment and we back up every machine via Netbackup currently. What is the real benefit I'd get to change my templates to use thin discs instead of thickness? This would allow an increase in performance in my environment? And... If there is such a great idea... Why VMware did not provide a way to deploy thin discs from the GUI already? I'm leaning towards the fact that it might introduce more questions and unknowns that she could never be interesting, but I'd like to receive comments from others before I draw my final conclusion. What do you say? Is this useful? Have you had experiences that you could share?

  Hello

  Unless you use NFS data warehouses, thin disks are a horrible idea except for the models. Don't forget that on the deployment of a model, whether thin or not, the VMDK resulting is thick discs.

  My post was more precisely to do with the optimization of the model and it is faster to deploy a model of thin-provisioned a supplied standard, more it uses less space on your SAN/NAS.

  See you soon,.

  Leo

  ---

  Leo Raikhman

  VMware/storage consultant

  http://blog.core-it.com.au

• Reservations of the thin disk growing cause SCSI?

  In the classic text on the origin of SCSI reservations, it is mentioned actions like adding new VMDK or remove snapshots them or expanding, but not permanent expansion / more and more thin disks. Are there reasons why the expansion of the thin disks does not cause this? If the size of the block VMFS is small that 1 MB the thin vmdk is developed probably quite often when the comments file system develops?

  It will take every time she needs to expand a SCSI reserve. Now, with the vsphere advanced locking mechanism a locking mechanism was relaxed if it shouldn\t be too big of a problem. In addition to this you could also, if your table is able, exploit VAAI capacity to unload the lock and do it on a level vs. block data store level.

  Yet once, talked with Satyam and you shouldn't be too worried. Especially if you do not overload the table/data store.

  Duncan (VCDX)

  Available now on Amazon: vSphere 4.1 HA and DRS technical deepdive

• How to get the VM with or without thin disk in VC Server

  I need to get my Vm list all in my server VC who have the fine disc and one of them is not a thin disk.

  I do not understand it can be done in CLI power and I have Vmware Vsphere CLI installed power. I also find some scripts on the net, but I don't know how to use them

  Please suggest step by step how to run these scripts and where console as well?

  Thank you

  Deepak

  If you have the names of these servers in a CSV file with this provision.

  Name
  server1
  server2
  ....
  

  You can use a script like this

  $report = @()
  Import-Csv "C:\My-Csv-file.csv" | %{
       $vm = Get-VM $_.Name
       $vm | Get-HardDisk | %{
            $row = "" | Select VMname, Folder, HDname, HDformat
            $row.VMname = $vm.Name
            $row.Folder = (Get-View $vm.FolderId).Name
            $row.HDname = $_.Name
            $row.HDformat = $_.StorageFormat
            $report += $row
       }
  }
  $report | Export-Csv "C:\VM-disk.csv" -NoTypeInformation -UseCulture
  

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Analysis of thin disk

  We're under ESX 4.0 and want to start building virtual machines with thin disks. 3rd party monitoring (ipMonitor) allows us to follow for the use of disk space on our virtual machines. I wonder how / if it is possible to monitor disk space on thin disks. If they can grow to any size they want how monitoring software will know where the alarm?

  Thank you

  Scott

  If you have the drive put in end service for your C and D size to 20 GB disks - no virtual disk will never exceed 20 GB - or take more than 40 GB of disk space - you have to worry is if you overcommitt the VMFS data store - Let's say you have 6 of these machines, sitting on a data store VMFS 200 GB - each with a C and D the service end disc size for 20 GB - initially each disc only has 5 GB of disk spaced used - initially then each computer virtual when turned off will consume 10 GB for a total of 6 x 10 GB or 60 GB of VMFS data store - when virtual machines get lit one by VM vmkernel swap file is created equal to the amount of memory assigned to the virtual computer minus the reserve - so the machines are running and that data is added to each virtual computer disks will thin provision to store that data, what are the consequences of the data store VMFS running out of space.

  1. If a virtual machine goes to additional data to the right and there is no space available on the OS of the VM data store will most likely by a clerical error and possibly crash

  2. If on virtual machines is powered off the coast and you try to turn it on and there is not enough space to create the by the VM vmkernel swap file it lights not

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Cannot convert thick disk of 10 GB on the thin disk

  I made the migration of storage a week ago to convert thin (10 GB hard drive) and he has succeeded at that time and I saw, it was transformed to thin. After a few days, it was automatically converted to thick. and it happened a few times already, also tried on a few other virtual machines that have 10GB, same thing happens, after a few days of thick back conversion.  I was wondering if there is no drive required to do the migration of storage? someone has an idea? I made large capacity disks more than 50 GB, they are very good. Just having trouble with low size disks

  -Thank you,

  Rahul

  John,

  When you do the storage vMotion, you selected a different data store then the one on which the virtual machine is? If this is not the case, try this one.

• VM disk thick / thin

  How will I know if the VM disk is supplied thickness / think?  Any tool vmware or 3rd party to verify vmdisk is thick / Think.

  If you change the settings of a virtual computer, look at the hard drive, and discover the type it will show if it is thick or thin provisioned.

  This was also moved to the course on vSphere storage forum.

  Post edited by: mittim12

• Can I convert a thin disk that is implemented in a thick disc put into service

  We run ESX4 Advanced Server as a standalone server.   No server VCenter.  The person who initially set up the server and the machine virtual used comments a provisioning and storage committed plu.  I have moved a few guests to another storage group and another host, but I would get all converted in thickness to avoid problems in the furture.  Is it possible to do with rebuilding the guest computers.

  Also how hard is it to resize the virtual disks and make them smaller.  For example, I have a few volumes of 50 GB using about 15 GB, I want to reduce to about 30 GB and recover the space.  Is this possible without having to reinstall the client o/s.

  Also if you know we do not use VMotion or VCenter.  Stand alone a few servers with local storage.

  Once again the quesiton so.  If I use the VMware Converter to change the thin provisioned in. thick, is it possible keep the virtual machine on the same host.  Whenever I used the converter, he sought a source and destination ESX server.  I do something wrong when I use it?

  Yes, when you use vConverter you can change thin thick (flat) also resize it. To use the same host, it is even not VM must appoint as before, you can put the same ESX host in source and destination. But then again, do not to use the same VM name. Good luck.

• 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

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

• FVO-exporters/OVA with already Thick-Provisioned disks?

  Hey guys!

  I was wondering, export OVA/OVF also shrink down thick disks configured?

  It would be great if she did it, because I have a VM swallow 4 TB of disk space that is to be exported, but only about 300 GB are currently used. (600 if taking into account RAID)

  Thank you!

  Hello

  Yes, he does. In addition, it will compress the data.

  Kind regards

  Patrick

• Immediate error prealloue expandable disk conversion

  Windows 7 x 64, vmware Workstation 12. I'm trying to convert a disk preallocated a growable since half of the 140 GB are not used.

  I entered the following command at the command line prompt:

  VMware - vdiskmanager.exe - r "D:\Virtual Machines\Server\C.vmdk" t 0 "D:\Virtual Machines\new.vmdk".

  Here is the output of this command:

  Creation of disc "D:\Virtual Machines\new.vmdk".

  NOT_REACHED bora\lib\disklib\diskLibMisc.c:483

  Using Win32 object: GDI 4, 1 USER

  CoreDump: Write minidump in C:\Users\J\AppData\Local\Temp\vmware-J\vmware-vdiskmanager.dmp

  Opening of the dmp file listed above give this point of failure:

  2016 01-19 T 11: 51:27.440 - 05:00 | vthread-4 | I125: VixDiskLib: VixDiskLib_Connect: establish a connection.

  2016 01-19 T 11: 51:27.440 - 05:00 | vthread-4 | I125: VixDiskLib: VixDiskLib_Clone: make a clone of disc.

  2016 01-19 T 11: 51:27.447 - 05:00 | vthread-4 | I125: DISKLIB-DSCPTR: open [0]: "4b955744f81011e380b4806e6f6e6963.datto" (0xe)

  2016 01-19 T 11: 51:27.447 - 05:00 | vthread-4 | I125: DISKLIB-LINK: open 'D:\Virtual Machines\Server\C.vmdk' (0xe): vmfs, 292945983 sectors / 139.7 GB.

  2016 01-19 T 11: 51:27.447 - 05:00 | vthread-4 | I125: DISKLIB-LIB: open 'D:\Virtual Machines\Server\C.vmdk' (0xe, type vmfs flags).

  2016 01-19 T 11: 51:27.447 - 05:00 | vthread-4 | I125: DISKLIB-LIB_CREATE: CREATE: 'D:\Virtual Machines\new.vmdk' - monolithicSparse ability = 0 (0 byte) adapter = invalid info = size = 128 political = objType = "

  2016 01-19 T 11: 51:27.450 - 05:00 | vthread-4 | I125: PANIC: NOT_REACHED bora\lib\disklib\diskLibMisc.c:483

  What causes this error and how can it be solved?

  Thank you

  Joe

  Now that was fun - thank you for the question.
  I can reproduce this now - he actually gives a good indication in the last line before the panic: invalid = adapter

  2016 01-20 T 02: 48:04.025 + 01:00 | vthread-4 | I125: VixDiskLib: VixDiskLib_Clone: make a clone of disc.

  2016 01-20 T 02: 48:04.040 + 01:00 | vthread-4 | I125: Hostinfo_OpenProcessBits: OpenProcess access bits are 1000.

  2016 01-20 T 02: 48:04.040 + 01:00 | vthread-4 | I125: FILE: FileLockScanDirectory throw g:\_vms_\monolithicflat.vmdk.lck M10277.lck': 27532-130977279873508300(vmware-vdiskmanager.exe) invalid executionID.

  2016 01-20 T 02: 48:04.056 + 01:00 | vthread-4 | I125: DISKLIB-DSCPTR: open [0]: 'monolithicflat - flat hard' (0xe)

  2016 01-20 T 02: 48:04.056 + 01:00 | vthread-4 | I125: DISKLIB-LINK: opened 'g:\_vms_\monolithicflat.vmdk' (0xe): vmfs, 292970496 sectors / 139.7 GB.

  2016 01-20 T 02: 48:04.056 + 01:00 | vthread-4 | I125: DISKLIB-LIB: open "g:\_vms_\monolithicflat.vmdk" (flags 0xe, type vmfs).

  2016 01-20 T 02: 48:04.056 + 01:00 | vthread-4 | I125: DISKLIB-LIB_CREATE: CREATE: 'g:\_vms_\vmfs-to-spars2ef.vmdk' - monolithicSparse ability = 0 (0 bytes) adapter = Invalid info size = 128 = political = objType = "

  2016 01-20 T 02: 48:04.056 + 01:00 | vthread-4 | I125: PANIC: NOT_REACHED bora\lib\disklib\diskLibMisc.c:483

  To cause the crash I gave an incomplete descriptorfile:
  (Incomplete - well after my own definitions at least - I don't know that if a minimum vmdk descriptor syntax should work with WS 12 has already been documented?
  Anyway - I guess you have to set

  version = 1

  CID = fffffffe

  parentCID = ffffffff

  createType = "VMFS".

  RW 292970496 VMFS "monolithicflat - flat hard."

  ddb.adapterType = "free".
  to be considered as minimal, but valid descriptor for a conversion action. Here, I get a crash if I set only

  version = 1

  CID = fffffffe

  parentCID = ffffffff

  createType = "VMFS".

  RW 292970496 VMFS "monolithicflat - flat hard."

  So it seems that vdiskmanager did not expect to ever see descriptorfiles that don't NOT definde ddb.adapter.
  It can handle a bad value as ddb.adapterType = "aunt-dorothies-favorite-sausage" with a useful error - but the parameter should be set.
  Doesn't really matter if - almost all of the descriptors automatically created should work - manual changes would be the only reason for which I could imagine as a possible reason...

  Maybe your problem is caused by the same similar thing? -fix would be easy to verify anyway.

  # Disk DescriptorFile

  version = 1

  #encoding = "windows-1252".

  CID = fffffffe

  parentCID = ffffffff

  createType = "VMFS".

  # Description of the measure

  RW 292970496 VMFS "monolithicflat - flat hard."

  # The database disk

  #DDB

  #ddb.adapterType = "free".

  #ddb.geometry.cylinders = "18236.

  #ddb.geometry.heads = "255".

  #ddb.geometry.sectors = "63".

  #ddb.virtualHWVersion = "10".

  Red vmdk descriptor crashes with core dump - blue descriptor works.

  # Disk DescriptorFile

  version = 1

  #encoding = "windows-1252".

  CID = fffffffe

  parentCID = ffffffff

  createType = "VMFS".

  # Description of the measure

  RW 292970496 VMFS "monolithicflat - flat hard."

  # The database disk

  #DDB

  ddb.adapterType = "free".

  #ddb.geometry.cylinders = "18236.

  #ddb.geometry.heads = "255".

  #ddb.geometry.sectors = "63".

  #ddb.virtualHWVersion = "10".

  Don't be surprised - I commented several ddb.parameters - for conversion, they aren't necessary, and I wanted to exclude no side effects using the smallest valid selection.

• POS on thin disk (free space < 850Go)

  Hi, I want to tho VDP to test before leaving VDR.

  I read in the literature, we can use the fine disc rather than thick disk to install VDP (I have enough disk space).

  But I n 't see this option during deployment of the device.

  I made a mistake?

  In VDR my backup to a windows share, were then backup upward on the Strip.

  With POS, what is the best practice to back up to tape because CIFS shares are not supported?

  Thank you.

  Hello

  See the attached screen, which displays the configuration option.

  2 VDP currently do not have a direct integration with tape. But to see if the (vSphere Data Protection Disaster Recovery) of the Administrator's guide help section.

• methods to follow the actual size of the thin disk

  In my environment, I'm above implement disk Thin Provisioning, for the purposes of the report, I need to monitor the actual size of the service end disc is there a tool or script that would help me to monitor disk size real of thin disc put into service.

  Get-VM VMNAME | Select name, usedspaceGB

  the usedspaceGB will give you the actual use.