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

Tags: VMware

Similar Questions

  • IP source routing should be disabled

    Hi team

    I need to disable the address IP source routing should be disabled on ucsmanager. can you please someone tell me where I can disable.

    If we disable may I know what is the impact that we will get.

    Thanks in advance

    Mohan

    Mohan,

    But there is no plan on FIs, NXOS routing data. Let me show you.

     bdsol-6296-01-B(nxos)# show ip route IP Route Table for VRF "default '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] bdsol-6296-01-B(nxos)# show ip route vrf management No IP Route Table for VRF "management" bdsol-6296-01-B(nxos)# sh run int mgmt 0 !Command: show running-config interface mgmt0 !Time: Fri Oct 16 11:02:50 2015 version 5.2(3)N2(2.23d) interface mgmt0 shutdown force ip address 10.48.43.82/25

    Hope that things cleared up.

    M.

  • NFS datastore on does not create the thick disk

    Hi Experts

    We have 4 and 5 from esx esx in our workplaces.

    I observed something strange with ESX 5, we cannot create thick disk for VM on NFS data warehouses

    While the same was collaborating with ESX 4. I'm still able to create thick disk using the same NFS volume.

    Nothing has changed in ESX 5.X? which does not allow users to create thick disk in NFS.

    Srinivas-

    NFS data with hardware acceleration warehouses and VMFS data storages are supported the following political drive of provisioning. On NFS warehouses that do not support hardware acceleration, that thin format is available. Link

  • How can change the end of thick disk when a virtual machine has been placed on the disk?

    After you have moved the virtual computer to another stage, chose the thin disk bad. Now, the virtual machine cannot start. the error message says that it must be thick for clustering. So, I need to change it back if possible. Then I moved it back and thick chosed. But, after that, I got a same error. So, after you move, the atatuse disk was not be changed. Is it a way not both directions? How can change the staus thin to thick?

    Thank you!

    George

    Hello George,.

    You can also convert virtual disks in eagerzeroedthick from the command line.

    vmkfstools-j VMname.vmdk allows to convert a thin disk in eagerzeroedthick

    vmkfstools k VMname.vmdk that will do it on a thick disk

    It can also work for a thin disk, click with the right button on the vmdk in browser data store, and then click 'inflate '.

    André

  • Storage motioned to VM with thick disk thin disc?

    Recently, we tried using SMotion to convert the current thick disk of our VM provisioning, but it won't expand the c:\ partition when we increase the size of the disk in the vSphere client. According to the official docs it is supported using SMotion so if anyone can help me I would be grateful.

    No, just launch extpart on the virtual machine that you want to extend the volume on (after you have extended the volume in the settings of the virtual machine) from the command line and you will be asked to provide the letter of volume, then the size of developing.   If you have trouble with it I can do a screen cast for you in my environment if it would help.

    ---

    If you have found any of my reviews useful please consider giving points to 'Correct' or 'useful '. Thank you!!!

    www.beyondvm.com

  • line should become updatble after clicking on the button update

    When the user interface is displayed line in the table is not the updateable (read only) when you click on the button update present at the top of the table at this time select a line button should become as editable. Can someone tell me how to do this. Thanks for your help.

    Hello

    in the table create text entries and now the ReadOnly property to bind a temporary variable of type Boolean.

    to do this use SPEL. ${oa.current.ViewAttribute}

    Now that the page loads all first set the transient true attribute. so that all lines are read-only.

    Now when you click on the update button, enter the event and the primary key of the row.

    To loop through the rows and if the primary key corresponds to that means that it is the line so on this set of rows of the
    attribute transient to be false so that become only that particular line can.

    There are many threads already for this purpose in the forum... look it up...

    Thank you
    Gerard

    Published by: Gauravv on October 28, 2009 04:29

  • How to find if a scsi disk can be used as a ROW or only use not vsphere CLI.

    Hi, I want to know if the SCSI disk can be used as RDM and a remote computer running vSphere CLI.

    I tried to use 'vicfg-scsidevs - l', but it doesn't have the required information list

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

    Here is sample out put

    MPX.vmhba0:C0:T1:l0

    Device type: disk

    Size: MB 69459

    Full name: disk space from VMware (mpx.vmhba0:C0:T1:L0)

    Plugin: NMP

    Device console: /vmfs/devices/disks/mpx.vmhba0:C0:T1:L0

    Devfs Path: /vmfs/devices/disks/mpx.vmhba0:C0:T1:L0

    Seller: VMware model: Block device Revis: 1.0

    SCSI level: 2 is nickname: status:

    : RDM Capable is removable:

    Other names:

    VML.0000000000766d686261303a313a30

    empty fields "Is Capable RDM" here.

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

    When I executed the command 'esxcfg-scsidevs - l' on an ESX Server, he gave me the necessary info.

    MPX.vmhba0:C0:t0:l0

    Device type: Direct access

    Size: 138919 MB

    Full name: disk space from VMware (mpx.vmhba0:C0:T0:L0)

    Plugin: NMP

    The console device: / dev/cciss/c0d0

    Devfs Path: /vmfs/devices/disks/mpx.vmhba0:C0:T0:L0

    Seller: VMware model: Block device Revis: 1.0

    : SCSI 2 is Pseudo: false status: on

    : RDM Capable false is removable: false

    Is Local: true

    Other names:

    VML.0000000000766d686261303a303a30

    So is it possible for vSphere CLI through which we can tell if the SCSI disk device can be used as ROW or NOT?

    and what parameter defined as capable of RDM?

    Thank you

    Chandra Sekhar P.

    Hi Chandra,

    In order to get the SCSI LUNS that can serve as RDM, you must use the QueryConfigTarget method. This method is defined on EnvironmentBrowser. You need to recover some EnvironmentBrowser object ComputeResource the HostSystem where the virtual machine is created. The configTarget.ScsiDisk returned after the method call contains the logic unit number information that is capable of RDM.

    I hope this helps!

    Neha

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

    disk.JPG

    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

    thindisk.JPG

    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

  • convert the eager Zerod thick disk

    I have shut down my db with disks FT migrated to another host server.

    Error message: cannot open (thin/TBZ disks cannot be opened in multiwriter mode.).

    This migration removed the formatting of the disk based on what I read in this article (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1033570) and I'm unable to turn on. Checked this and it looks like it was the case:
    Vim - cmd /vmsvc/device.getdevice 240 | grep-i 'Hard drive 5' - a 14
    label = "hard drive 5.
    Summary = "Ko 41,943,040."
    },
    backup = {(vim.vm.device.VirtualDisk.FlatVer2BackingInfo)
    dynamicType = < unset >
    fileName = "[iscsi_vsa_03] vmdb12/vmdb12_4.vmdk,"
    data store = ' vim. Datastore:4df78c93 - 28dd82b4 - 30 to 3-001b21378e78',.
    diskMode = "persistent."
    Split = false,
    writeThrough = false,
    thinProvisioned = false,
    eagerlyScrub = < unset >
    UUID = "6000C298-9a1e-41e5-674c-06f841d4c925."
    contentId = "162229b0fda7a14745246a8a3e255285."
    changeId = < unset >
    ~ #
    • If the virtual disk VMDK is a Thin, convert the eager Zerod drive of the thickness using the vmkfstools --inflatedisk command. For example:

      vmkfstools --inflatedisk /vmfs/volumes/DatastoreName/VMName/VMName.vmdk


      Note: the command of inflation indicates the percentage of completion.

    • If the VMDK virtual disk is thick, convert the drive eager to zero thickness using the vmkfstools --eagerzero command. For example:

      vmkfstools --eagerzero /vmfs/volumes/DatastoreName/VMName/VMName.vmdk

      Note: the avid zero order does not indicate the percentage of completion.

    1. do I need to run the two commands?

    2 will. that affect data on these discs?

    Hello.

    The disc is not thin provisioned (thinProvisioned = false), then the command ' vmkfstools - inflatedisk ' is not necessary.  Running the ' vmkfstools - eagerzero "command should not affect all data on the disk, but it is always a good idea to make sure that you have a backup before you run all disk commands.

    Good luck!

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

  • Thin and thick disks on the same virtual machine?

    Is this possible with vsphere ESX 4... to have a disc thin and thick, attached to the same Virtual Machine... ? Is this documented place... ?

    Thanks,-Nicodemus

    Yes...

    Page 247

    http://books.Google.com/books?id=b12tupvbqEAC&PG=PA247&LPG=PA247&DQ=VMware mixingthinandthick+disk&source=bl&ots=FOCD-X9lMP&sig=z720_K5b3M99GfOLqtlBkeixXBU&hl=en&ei=YkAhTOWCMcbonQeL4MRy&sa=X&oi=book_result&ct=result&resnum=3&ved=0CCcQ6AEwAg#v=onepage&q=It%27s%20possible%20for%20a%20VM%20to%20have%20a%20mix%20of%20both%20thick%20and%20thin%20virtual%20disks&f=false

  • Need advice on thin or thick disk

    I need to install a few servers with openSuse11.1x64 and Oracle11.1 on vSphere4 and esx4i. Each server has a data store of 1 GB on the shared SAS storage.

    The databases will grow up to 1 TB.

    I have a big dilemma, what type of disc it is (thin or thick) and which is usually the best practice in this situation?

    I notice, for example, if I create a thickness of 1 TB disk, after that one or two snapshoot an error disk is full. If I create a thin disk it does not error, but what about thin disk IO performance?

    Thanks to all the good advice.

    Hello

    1 Vmware tools on openSUSE are "obsolete." How do I install them?

    The 'normal' fact. Select "Update VMware Tools" in the menu VM and OpenSUSE should see the latest VMware Tools CDROM. Maybe then you will need to run the installer of your self... However, if you use open VMware tools is another topic and there anotehr forum for this. The way to tell is to look at your list of openSuse packages and checks if there is a package named open-vm-tools, if yes, then you are using the open version. Let me know if I can redirect to the right position.

    2. If I did only a single VM on the server, the number of vCPU and memory is the best option?

    Do you plan on adding several virtual machines?

    3. my datastore has 4 MB block size because I need the 1 TB drive. Is this ok? Can I create with the lower block size 1 TB drive.

    N ° to create a 1 to VMDK file, you need the largest block size.

    For a VMFS with > 2 TB - 512 bytes of space, you would use "Extensions" to bring together multiple LUNS up to 64 TB - 512 byte MAX. There is an option to consider going forward... However, a single VMDK can only be 2 TB you would then look to add new disks and for strong transactional use DB I would forget in fact on the use of vmdk in all.

    In your case, I would use Raw Disk cards out of your storage device... Not VMDK and use several RDM for data/logs/etc.

    Best regards
    Edward L. Haletky VMware communities user moderator, VMware vExpert 2009

    Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

    Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

    Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

    Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

  • 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

  • VMWare esxi 5.5 - is possible to shrink a thick disk hard put into service?

    Hey guys

    Recently, I have increased the size of the hard drive to one of my VM to 300 GB drives when I only need 200GB.

    The player is supplied thickness. Memory I don't think that you can reduce a thick disc put into service from the client VMWare 5.5.

    So my question is, is there another way I can reduce this hard drive stocked thickness so I can recover unused space?

    Kind regards

    Aaron

    Yes, technically, if you have a 300 GB windows volume supported by a thick hard of 300 GB you can do the following:

    1. Defragment system files comments with Raxco Disk defrag or similar, as the use of the option consolidate free space
    2. Try and make sure that a good number costs blocks by the end of the partition (options defrag boot use pagefile and $mft etc.)
    3. Reduce the 200 GB partition
    4. Storage vmotion virtual machine and set the destination thin format

    This hard never will now have more than 200 GB unless the windows partition is cultivated but the hard remains thin. Otherwise, vmware standalone converter or vmkfstools way to go. If prefer vmkfstools.

  • Unable to connect the existing thick disks in VM

    Hello

    I am trying to establish a connection between a series of existing virtual disks and some virtual machine. So far, I was able to connect to all my discs thin-set in service without any problem with the following line:

    $targetVM | New-harddisk - DiskPath ($disk. File name)

    However, it seems that this command does not always work when it comes to thick-set disks in service, resulting in the following error message:

    http://PUU.sh/9xBs9/a73fd64b20.PNG

    I'm trying to get a work around for thick discs, but I'm out of ideas.

    Thanks in advance.

    Take a look on Re: adding copied the hard disk (VMDK) to a virtual machine

Maybe you are looking for