storage vmotion requirements/limitations - vsphere (Full Version)

All Forums >> [VMware Virtualization] >> Storage Management



Message


virtualrape -> storage vmotion requirements/limitations - vsphere (23.Sep.2010 6:20:17 PM)

Looking for a doc on storage vmotion requirements and limitations in Vsphere - cant find one anywhere - anyone recommend?




JustinC71 -> RE: storage vmotion requirements/limitations - vsphere (24.Sep.2010 10:19:30 AM)

Check out the Datacenter Admin Guide, page 214.

http://www.vmware.com/pdf/vsphere4/r41/vsp_41_dc_admin_guide.pdf


quote:

Storage vMotion Requirements and Limitations
A virtual machine and its host must meet resource and configuration requirements for the virtual machine
disks to be migrated with Storage vMotion.
Storage vMotion is subject to the following requirements and limitations:
- Virtual machines with snapshots cannot be migrated using Storage vMotion.
- Virtual machine disks must be in persistent mode or be raw device mappings (RDMs). For virtual
compatibility mode RDMs, you can migrate the mapping file or convert to thick-provisioned or thinprovisioned
disks during migration as long as the destination is not an NFS datastore. If you convert the
mapping file, a new virtual disk is created and the contents of the mapped LUN are copied to this disk.
For physical compatibility mode RDMs, you can migrate the mapping file only.
- Migration of virtual machines during VMware Tools installation is not supported.
- 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 in order to perform migration with Storage vMotion.
- The host on which the virtual machine is running must have access to both the source and target datastores.
- For limits on the number of simultaneous migrations with vMotion and Storage vMotion, see “Limits on
Simultaneous Migrations,” on page 227.  




Page: [1]