VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications Page 116

  • Download
  • Add to my manuals
  • Print
  • Page
    / 146
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 115
Migration with Storage vMotion
Using Storage vMotion, you can migrate a virtual machine and its disk files from one datastore to another
while the virtual machine is running.
You can choose to place the virtual machine and all its disks in a single location, or select separate locations
for the virtual machine configuration file and each virtual disk. The virtual machine does not change execution
host during a migration with Storage vMotion.
During a migration with Storage vMotion, you can transform virtual disks from thick-provisioned to thin-
provisioned or from thin-provisioned to thick-provisioned.
Storage vMotion has a number of uses in administering virtual infrastructure, including the following
examples of use:
n
Upgrading datastores without virtual machine downtime. You can migrate running virtual machines from
a VMFS2 datastore to a VMFS3 datastore, and upgrade the VMFS2 datastore using a two step process.
You can then use Storage vMotion to migrate virtual machines back to the original datastore without any
virtual machine downtime. For information on upgrading VmFS2 to VmFS5, see the vSphere Storage
documentation.
n
Storage maintenance and reconfiguration. You can use Storage vMotion to move virtual machines off of
a storage device to allow maintenance or reconfiguration of the storage device without virtual machine
downtime.
n
Redistributing storage load. You can use Storage vMotion to manually redistribute virtual machines or
virtual disks to different storage volumes to balance capacity or improve performance.
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:
n
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 thin-
provisioned 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.
n
Migration of virtual machines during VMware Tools installation is not supported.
n
The host on which the virtual machine is running must have a license that includes Storage vMotion.
n
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.
n
The host on which the virtual machine is running must have access to both the source and target datastores.
n
For limits on the number of simultaneous migrations with vMotion and Storage vMotion, see “Limits on
Simultaneous Migrations,” on page 134.
vCenter Server and Host Management
116 VMware, Inc.
Page view 115
1 2 ... 111 112 113 114 115 116 117 118 119 120 121 ... 145 146

Comments to this Manuals

No comments