It is possible to Storage vMotion virtual machines that have snapshots?

It is possible to Storage vMotion virtual machines that have snapshots?

A.
True

B.
False

6 Comments on “It is possible to Storage vMotion virtual machines that have snapshots?

  1. Anitha says:

    The correct answer is B: False
    See:
    http://pubs.vmware.com/vsphere-50/index.jsp?topic=/com.vmware.vsphere.storage.doc_50/GUID-8AE88758-20C1-4873-99C7-181EF9ACFA70.html

    Migration of virtual machines with snapshots is possible if the virtual machine resides on shared storage accessible to source and destination hosts.

    Some restrictions apply when migrating virtual machines with snapshots. You cannot migrate a virtual machine with snapshots with Storage vMotion. Otherwise, migrating a virtual machine with snapshots is permitted, regardless of the virtual machine power state, as long as the virtual machine is being migrated to a new host without moving its configuration file or disks. (The virtual machine must reside on shared storage accessible to both hosts.)

  2. Anitha says:

    Sorry the link takes to generic topic . in the vmware pubs page , goto – ESXi and vCenter Server 5.0 Documentation > vCenter Server and Host Management > Migrating Virtual Machines > Migration with Storage vMotion

  3. tom ku says:

    Storage vMotion Requirements and Limitations
    You can migrate virtual machine disks with Storage vMotion if the virtual machine and its host meet the following resource and configuration requirements:

    For ESXi 5.0 hosts, you can migrate virtual machines that have snapshots. For earlier versions of ESXi, you cannot migrate virtual machines that have snapshots.

    Virtual machine disks must be in persistent mode or be raw device mappings (RDMs). For physical and virtual compatibility mode RDMs, you can migrate the mapping file only. For virtual compatibility mode RDMs, you can use the vSphere Client to convert to thick-provisioned or thin-provisioned disks during migration as long as the destination is not an NFS datastore. You cannot use the svmotion command to perform this conversion.

    The host on which the virtual machine is running must have a license that includes Storage vMotion.

    ESX/ESXi 3.5 hosts must be licensed and configured for vMotion. ESX/ESXi 4.0 and later hosts do not require vMotion configuration to perform migration with Storage vMotion.

    The host the virtual machine is running on must have access to both the source and target datastores.

    A particular host can be involved in up to four migrations with vMotion or Storage vMotion at one time. See “Limits on Simultaneous Migrations” in the vCenter Server and Host Management documentation for details.
    If you use the vSphere Client for migration with svmotion, the system performs several compatibility checks. These checks are not supported by the svmotion vCLI command.

  4. Cals says:

    Storage vMotion was alien in 2007 for the aboriginal time. We’ve apparent a lot of improvements over time to the appearance accompanying to VM clearing technologies. Accumulator vMotion allows an active VM to be confused from one abstracts abundance to addition abstracts store. My accumulator convenance about sees me application VMFS volumes for vSphere VMs, but NFS is additionally accurate for Accumulator vMotion.

    vMotion Storage


Leave a Reply

Your email address will not be published. Required fields are marked *