Shared-nothing vMotionĪlso known as vMotion without shared storage, allows you to utilize vMotion to migrate virtual machines to a different compute resource and storage simultaneously. When you choose to change both the host and the datastore, the virtual machine state moves to a new host and the virtual disks move to another datastore. Storage vMotion is the migration the files, that belong to a running virtual machine, residing on one discrete datastore to another discrete datastore. Compute vMotionĬompute mode vMotion operations usually occur within the same logical vSphere cluster, The two hosts involved in a vMotion can, however, reside in separate logical or physical clusters. If errors occur during migration, the virtual machine reverts to its original state and location. vMotion operations are transparent to the virtual machine being migrated. Also, you can use vMotion to migrate virtual machines across: vCenter Server instances virtual and physical data centers and subnets. Migration of a virtual machine can be either compute only, storage only or both simultaneously. We will cover topics including migration within an existing data center with both shared and non-shared storage, from physical servers direct to vSAN and migrating between physically disparate data centers. Recommendations presented are based on current VMware best practices. While third-party options and solutions, such as backup, recovery, and replication are valid options those items are out of scope for this document due to extra cost and resources involved to deploy, configure and implement. Minimal or no reconfiguration will be emphasized as well as maintaining virtual machine uptime, avoiding downtime where possible. The methodologies presented are valid for vSAN in general, vSAN Ready Nodes clusters as well as hyperconverged infrastructure (HCI) appliances such as Dell EMC VxRail™ Appliances. This article will discuss the native options for migrating virtual machine workloads to vSAN. Migration strategies and options for vSAN are numerous depending on your environment and implementation of vSphere.
0 kommentar(er)
