Storage vmotion and vsphere 4.1 eval

Hello

I use vsphere 4.1 (eval version). I have two hosts with shared storage.  I have installed vcenter and the two added hosts.

When I try to storage vmotion, a virtual machine, I find that the "Change host and data store" option is grayed out.

Under the option greyed out is the line "the VM must be power off to change the virtual host machine and data store"

When I look at 'Features licensed' I see "Storage vMotion" is available.

Any ideas why I can't storage vmotion?

Thank you very much

p.s Someone can tell me are the different versions of vsphere Essentials that is, Standard, Enterprise, Enterprise more etc, in fact different pieces of software or the other a difference of license?

What you have selected is not a Storage vMotion.  If you want to change the data store, you cannot change the host at the same time.  If you change hostm you cannot change the data store at the same time.

Choose one or the other.

-Matt

VCP, VCDX #52, Unix Geek, Nerd of storage

Tags: VMware

Similar Questions

  • Please explain SVmotion (Storage Vmotion) and DRS for storage in simple words

    Friends,

    I little confusing... could you please contact Storage vmotion and DRS for storage in simple words and the important points to remember in this regard...

    Kind regards

    Sirot

    9884106697

    Storage DRS is a feature that you allow warehouses of data aggregated on a single object (cluster) and recommend the implementation of disks in virtual machine based on the performance of the store of data and the available space on the data store.

    The DRS storage uses Storage vMotion to migrate virtual (online) computers from a data store to another to balance data store performance and space.

    You can use Storage vMotion without storage DRS too, moving virtual machine between clusters of DRS storage and warehouses of data even from the local level to the data store shared.

  • Readers of Storage VMotion and RDM

    Running vSPhere 4.0 and ESX 3.5. I'm migrating to vSPhere. This question is about the servers Windows 2003 running on ESX 3.5 U4.

    I have a couple of file servers that have a basic virtual disk and also one or more readers added through RDM. I want to migrate the Basic virtual disk to a different LUN storage for cleaning. Are the questions with the help of the storage vmotion on the vSphere client to migrate to a different LUN storage? I'm not trying to move the RDM, just the virtual disk storage and the VM files?

    When SVmotion VMs select only basic disk to migrate then. Otherwise RDM will be migrated too and become VMDK.

    But you can also disconnect RDMs first and them just VMs SVMotion completely.

    ---

    MCSA, MCTS, VCP, VMware vExpert 2009

    http://blog.vadmin.ru

  • Storage vMotion and RDM

    I have a question for you about storage vMotion. I have a virtual machine with a vmdk file and a RDM. I want to storage vmotion the vmdk file. There is also a file associated with the ROW pointer. How this pointer file is reassocie to the RDM? I'm evacuating small LUNS and move virtual machines to the largest lun.

    On page 199 and 201 of the basic ESX Administrator's Guide, it states that, if I select "same as Source for a RDM, only the mapping file will be migrated. Have you done this before? I just wanted to see if anyone in the field has had an experience with this process.

    7. If you chose to move the virtual machine configuration file and virtual disks, select a disc format, and then click

    Next.

    Description of the option

    Same as Source to use the format of the original virtual disk.

    If you select this option for a RDM in physical or virtual drive

    compatibility mode, only the mapping file is migrated.

    Thin provisioned using the format thin to save storage space. The thin virtual disk use as

    storage space because it needs for its initial implementation. When the virtual disk

    needs more space, it can grow in size up to its maximum allowed of capacity.

    This option is not available for RDM in physical compatibility mode. If you

    Select this option for a virtual RDM compatibility mode, the ROW is

    converted to a virtual disk. RDM converted virtual disks cannot be

    converted into RDM.

    Thick allocate an amount fixed disk space for the virtual disk. The virtual

    drive in thick format does not change its size and from the beginning

    occupies the entire data store space for her.

    This option is not available for RDM in physical compatibility mode. If you

    Select this option for a virtual RDM compatibility mode, the ROW is

    converted to a virtual disk. RDM converted virtual disks cannot be

    converted into RDM.

    Thank you

    Savoy6

    Hi Savoy6,

    When you sVmotion a virtual machine with a disc RDM, the pointer file is re-created on the new location and points to the raw LUN.

    Take a look at this kb for more information.

    It may be useful

    Concerning

    Franck

  • Storage vmotion and SRM

    Hi guys,.

    Another question.

    How SRM cope with moving LUNS replicated and not replicated virtual machines?

    In blog of eppings duncan, he created agreat SRM FAQ. Inside, he mentions the following:

    What happens if you move one of the virtual machine that is protected in a data store that is not part of the current protected group of the virtual machine?

    Protection is revoked for the virtual machine. There will be a small yellow

    triangle associated in the protection group. This will be true

    even if you move (for example, storage VMotion) the virtual machine to a different

    store data that is replicated to the recovering site.

    If at this point, how do you take the virtual machine out of the protection group or add the virtual machine in the protection group?

    Thank you

    DC

    A new analysis of storage using the Array Manager Setup Wizard will clarify this point.

    See you soon

    Tim Oudin

  • Storage VMotion and what it actually does?

    Hello

    I recently started to use the VM to my new company and I am migrating various VM out of ESX host for them (level 4 of ESX 3.5 Patch) patch.

    Now, I met my first VM installed on a local storage on an ESX host. I understand that I must use Storage VMotion to migrate this and that there is a plug-in that allows you to do so (SVMotion VI-Client Plugin). I also read the prerequisites for Storage VMotion Administrator's guide and I covered.

    However, I do not entirely understand, what this process done. On an online resource that I found it says the following "However, with SVMotion the VM guest stays on the server it resides on but the Ramdisk that VM is what is happening."  Now, if I need to restart this ESX host is that this goes to the impact of this machine virtual comments?

    I do not understand what this distinction between 'Comments' and 'VM virtual disk' would mean in terms of impact on the system for the service providing VMS.

    Notice to lovers?

    Tom

    Storage VMotion allows you to migrate pwered VM transparently to end users. But you can always turn off the virtual machine and migrate to another data store.

    ---

    MCSA, MCTS, VCP, VMware vExpert 2009

    http://blog.vadmin.ru

  • Storage VMotion and VC update 4

    Hi, can you tell me if Storage VMOTION is included in update 4 VC using VC client infrastructure?

    Or CLI is always required to use this feature with a specific plugin?



    Best regards

    Hello.  I just upgraded and do not see it there.  I use the SVMotion plugin , and it still works perfectly.

  • Storage Vmotion and Volume names

    I'm testing the ability to move a virtual machine that has 4 virtual disks (disks are named as follows vm_d, vm_f, vm_c, vm_g). I want to leave two of the disks where they reside and only to move two disks (vm_f and vm_g). I got it works however I noticed that when I look at the discs displaced the VMDK names have changed. Vm_f and vm_g discs are now just named vm.vmdk. Is there a way to make sure that the vmdk name does not change when the disc is moved? I don't want to rename the disk I want to just move to a different logic unit number.

    Thank you.

    The side effect, and more often an advantage, move your vm disk files, is that the name of the discs are updated to reflect the name of the virtual machine.  If this is done by cold migration or svmotion, the result is the same, the disks will be renamed.

    -KjB

  • County of vMotion and Storage vMotion over the last 24 hours

    I am under the below a line to count the number of vMotion and Storage vMotion, which happened in the past 24 hours in the middle and it not give me the required result, but when I combine them in the script that I use to collect additional information, it's just returns 0 (zero) as the County.

    Rely on Storage vMotion and vMotion

    Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

    Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} |

    Measure-object | Select-Object - ExpandProperty County

    Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

    Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} |

    Measure-object | Select-Object - ExpandProperty County

    Combined script

    Get-Cluster |

    {ForEach-Object

    $Cluster = $_

    $VMHost = $Cluster | Get-VMHost

    $CpuUsageMhz = $VMHost | Measure-object-property CpuUsageMhz-sum | Select-Object - ExpandProperty sum

    $CpuTotalMhz = $VMHost | Measure-object-property CpuTotalMhz-sum | Select-Object - ExpandProperty sum

    $MemoryUsageGB = $VMHost | Measure-object-property MemoryUsageGB-sum | Select-Object - ExpandProperty sum

    $MemoryTotalGB = $VMHost | Measure-object-property MemoryTotalGB-sum | Select-Object - ExpandProperty sum

    $Cluster | Select-Object - property @{Name = "ClusterName"; Expression = {$_.} Name}},

    @{Name = 'vSphere HA'; Expression = {$_.} HAEnabled}},

    @{Name = 'Analysis HA-Host'; Expression = {$_.} ExtensionData.Configuration.DasConfig.HostMonitoring}},

    @{Name = 'HA-Failover capacity'; Expression = {$_.} ExtensionData.Summary.CurrentFailoverLevel}},

    @{Name = 'HA-Admission Control'; Expression = {$_.} HAAdmissionControlEnabled}},

    @{Name = 'Configuration problem'; Expression = {[string]: join (",", ($_.))} ExtensionData.ConfigIssue | {{(Select-ExpandProperty FullFormattedMessage))}}.

    @{Name = 'vSphere DRS'; Expression = {$_.} DrsEnabled}},

    @{Name = "The DRS automation level"; Expression = {$_.} DrsAutomationLevel}},

    @{Name = "Use of the CPU (Mhz)"; Expression is {$CpuUsageMhz}},

    @{Name = "Cpu (Mhz) Total"; Expression is {$CpuTotalMhz}},

    @{Name = 'Cpu use (%) » ; {Expression = {[Math]: Round(100*$CpuUsageMhz/$CpuTotalMhz)}},

    @{Name = "use (GB) of memory"; Expression is {$MemoryUsageGB}},

    @{Name = "Total (GB) of memory"; Expression is {$MemoryTotalGB}},

    @{Name = 'use of memory (%) » ; {Expression = {[Math]: Round(100*$MemoryUsageGB/$MemoryTotalGB)}},

    @{Name = 'VMS NB'; Expression = {$_ |} Get - VM | Measure-object | {{Select-Object - ExpandProperty County}},

    @{Name = 'Virtual machines without VMXNET3 NB'; Expression = {$_ |} Get - VM | Get-NetworkAdapter | WHERE-object {$_.} Type - not "Vmxnet3"} | Measure-object | {{Select-Object - ExpandProperty County}},

    @{Name = 'VMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} | Measure-object | {{Select-Object - ExpandProperty County}},

    @{Name = 'SvMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} | Measure-object | {{Select-Object - ExpandProperty County}}

    } |

    Export-Csv "C:\Script\Clusters.csv" - NoTypeInformation - UseCulture

    Could you please someone check the script above and let me know if there is something wrong

    Thank you!!

    But wait a minute, you mean that the "Num vMotions" and "Num of SvMotions" properties have a value of 0?

    This is normal, since you ask for events for the entity of the group, while you should do it for all the virtual machines in the cluster.

    Try the attached version.

  • Query vMotion and Storage vMotion events

    Hello

    I found the attached script on the site of Alan and it works very well in the listing of vmotion for a period of time selective event. I have been asked to do the same thing for Storage vMotion and would like to try this if possible in a single query.

    Thank you

    Take a look at get vMotion/svMotion history.

    When you have events, it will be easy to calculate meters through a Measure-Object cmdlet.

  • Isolate the vMotion and storage traffic?

    We use ESXi 5.1 using two physical switches for management traffic and two physical switches for VM and storage vMotion traffic. We use a DVSwitch with VLANS separated for VMs (125), storage (126) and vMotion traffic (127). My question is really about the physical switch setting. I have installation of VLANs, 125, 126 and 127 on my main switch with each of them having a layer 3 interface. I think that only the network of the VM (vlan 125) needs a layer 3 interface. In other words, my VLAN storage and vMotion is not routable by removing the 3 layer interface.

    Does this sound correct?

    Another twist, I have a Juniper switch where all layer 3 interfaces are defined. It is connected to 4 switches in the rear of my IBM Bladecenter. Two of these switches are Cisco 1 GB switches that carry all traffic to the management through a vSwitch network. The other two switches are BNT 10 GB switches that carry traffic for Storage vMotion and VMs. Of course, it's a network connection, because it carries several VLANS.

    My only question now is should I eliminate interface layer 3 on my storage network located on one vlan separate

    Well, you need your storage system accessible on these IP addresses by the systems for the management of the other subnets or such? You already have all traffic from subnet inter between iSCSI and other networks? If this isn't the case, then there is no need to have routable iSCSI network.

    For the ESXi hosts themselves there is usually zero reason to have vmkernel iSCSI interfaces be routable since you already do management etc on another routable network (and responses of hosts would be sent there as well except if you define static routes custom).

  • Storage vMotion with snapshots

    I'm trying to implement storage vMotion in vSphere and I wanted to try to clarify some of the requirements.  3.5, VMS with snapshots could not be SVM' ed.  This has now changed in 4.1 or anyone know if it will change in the future?  Does anyone found a workaround for this limitation?

    Thank you

    Currently, there is no work around for this.  The only way is to commit snapshots, then svMotion above.  Who knows what will be the next major version to the table well!

    If you have found this helpful at all prices please points using the correct or useful!  Thank you!

  • Storage vmotion, leaving something behind

    Hello

    I have a little problem with vsphere storage vmotion.

    I test vsphere storage vmotion, and I discovered that it somehow

    always leave something on the old data store.

    The virtual machine I'm currently move is called "MSCS1" has 1 disk of 10 GB.

    I'm trying to migrate storage of this virtual machine from a data store called ESXDATASTORE1 in another data store called ESXDATASTORE2

    Then the control where the virtual machine files are currently stored nuer the Summary tab,

    She states that this VM is on ESXDATASTORE1.

    I decided to go this virtual machine storage ESXDATASTORE2:

    I choose the option "change datastore.

    I select ESXDATASTORE2 as destination

    In the advanced options I select also datastore ESXDATASTORE2 as the destination for the "configuration file".

    and for "disk 1".

    For the disc format, I select "same as source format".

    When the storage vmotion ends, however,

    I have the following problem:

    In the summary of vm Properties tab.

    When I check on what data store, the virtual machine is rightnow,

    He says that he now has data on two data warehouses:

    ESXDATASTORE1 and ESXDATASTORE2.

    However, when I browse datastore ESXDATASTORE1.

    It seems to be that nothing of VM "MSCS1" there, the 'MSCS1' file is missing.

    When I browse ESXDATASTORE2, all files in VM MSCS1 seem to be there.

    Does anyone have an idea what this virtual machine data are to stay behind on ESXDATASTORE1 and where?

    Why the information in the show of the Summary tab that the data in the MSCS2 VM are now on 2 data warehouses?

    is this a bug?

    If I would delete datastore ESXDATASTORE1 now

    VM MSCS1 should always be working?

    Anyone who encountered this?

    Is this some sort of bug?

    Or I'm just something wrong here?

    Take a look at the parameters of the virtual machine.

    There could be a reference to the former datasore, for example an ISO attachment on the CDROM drive...

    André

  • ESX 4.0 Storage vMotion

    I'm looking for a good doc or webenar on storage vMotion

    Storage VMotion is integrated in VSphere if you are using the Evaluation Version or are licensed for use with the version of VSphere that you use.

    To use Storage VMotion, right-click the virtual machine and choose migrate - if you have a license for Storage VMotion, and multiple LUNS which Storage VMotion can use then you should see the choice for host of change, change or change host and storage storage.

    Datto

  • Storage vmotion very slow

    Storage vmotions run very slowly. The virtual machine that has a 60 GB HARD drive. I tried different storage and still the same result. I have even upgraded to a network of 10 GB with the same results. I opened an evidence of support and the engineer told me vmotion will not use the link in full speed but it seems quite slow for the numbers I get. I hope I have provided enough information below for assistance. I hope that it is something I am doing wrong...

    Hosts:

    3 x ESXi host. Two are updated to version 6.0 1 and a version 5.5.

    Dell PowerEdge R610

    Xeon E5540 - 8 x 2.53GHz

    48 GB OF RAM

    10 GB for storage and vmotion traffic

    4 x 1 Gb NIC for vm traffic interconnection

    All storage is on the shared storage. The only local thing is the operating system

    VMware EVC mode for the production of Intel's Nehalem.

    Storage

    Supermicro NAS 2 to 4 x 4 RAID 10 storage pools

    Integrated 10 GB NIC

    QNAP TS - 469U - PR to 4 x 4 RAID 5 NAS

    2 x 1 GB NIC aggregated link

    Network

    All 3 hosts and NAS are connected with a Netgear dedicated 10 GB switch (low-end model).

    Using a standard vswitch

    Problem

    1 ESXi host has a computer virtual stored on storage on NAS Supermicro 1 pool. When a storage vmotion is running on a virtual machine that has a 60 GB VMDK, it takes a long time to complete. He started at 09:36, and is now 61% fine at 10:58.

    2. the network of 10 GB is where the vmotion traffic is allowed.

    3. If I use a link to 10 GB or a 1 GB link, I get the same speed.

    4. I have disabled all VM at a time given for the trial and who has not helped either.

    5. I tried a QNAP so storage vmotion, and I get the same speed.

    I use connection CAT6A cables. I have fine tuned for storage, and it seems to work better now. Seems to be linked to "writing - sync" as ESXi.

Maybe you are looking for