You can move a virtual machine to another host and move its disks or virtual machine folder to another datastore. With vMotion, you can migrate a virtual machine and its disks and files while the virtual machine is powered on.
You can perform vMotion in environments without shared storage. Virtual machine disks or contents of the virtual machine folder are transferred over the vMotion network to reach the destination host and datastores.
To make disk format changes and preserve them, you must select a different datastore for the virtual machine files and disks. You cannot preserve disk format changes if you select the same datastore on which the virtual machine currently resides.
Verify that your hosts and virtual machines meet the necessary requirements. See Requirements and Limitations for vMotion Without Shared Storage.
- Right-click the virtual machine and select Migrate.
- To locate a virtual machine, select a datacenter, folder, cluster, resource pool, host, or vApp.
- Click the Related Objects tab and click Virtual Machines.
- Select Change both host and datastore and click Next.
- Select the destination resource for the virtual machine migration.
- Select a destination host or cluster for the virtual machine, and click Next.
Any compatibility problems appear in the Compatibility panel. Fix the problem, or select another host or cluster.
Possible targets include hosts and fully automated DRS clusters. You can select a non-automated cluster as a target. You are prompted to select a host within the non-automated cluster.
- Select the format for the virtual machine's disks.
Same format as source
Use the same format as the source virtual machine.
Thick Provision Lazy Zeroed
Create a virtual disk in a default thick format. Space required for the virtual disk is allocated during creation. Any data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine.
Thick Provision Eager Zeroed
Create a thick disk that supports clustering features such as Fault Tolerance. Space required for the virtual disk is allocated at creation time. In contrast to the thick provision lazy zeroed format, the data remaining on the physical device is zeroed out during creation. It might take longer to create disks in this format than to create other types of disks.
Use the thin provisioned format. At first, a thin provisioned disk uses only as much datastore space as the disk initially needs. If the thin disk needs more space later, it can grow to the maximum capacity allocated to it.
- Assign a storage policy from the VM Storage Policy drop-down menu.
Storage policies define the storage capabilities that are required by the applications running on the virtual machine.
- Select the datastore location where you want to store the virtual machine files.
Store all virtual machine files in the same location on a datastore.
Select a datastore and click Next.
Store all virtual machine files in the same Storage DRS cluster.
Select a Storage DRS cluster.
To not use Storage DRS with this virtual machine, select Disable Storage DRS for this virtual machine and select a datastore within the Storage DRS cluster.
Store virtual machine configuration files and disks in separate locations.
For the virtual machine configuration file and for each virtual disk, select Browse, and select a datastore or Storage DRS cluster.
If you selected a Storage DRS cluster and do not want to use Storage DRS with this virtual machine, select Disable Storage DRS for this virtual machine and select a datastore within the Storage DRS cluster.
- Select the migration priority level and click Next.
Reserve CPU for optimal VMotion performance
vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotion. vCenter Server grants a larger share of host CPU resources. if sufficient CPU resources are not immediately available, vMotion is not initiated.
Perform with available CPU resources
vCenter Server reserves resources on both the source and destination hosts to be shared among all concurrent migration with vMotion. vCenter Server grants a smaller share of host CPU resources. If there is a lack of CPU resources, the duration of vMotion can be extended.
- Review the information on the Review Selections page and click Finish.
vCenter Server moves the virtual machine to the new host and storage location. Event messages appear in the Events tab. The data that appears in the Summary tab shows the status and state throughout the migration. If errors occur during migration, the virtual machines revert to their original states and locations.