Part I:VMware virtual machine migration types vSphere 6.0

Welcome to new series of articles on virtual machine migrations.

So let’s get started with first one. Here we will talk about migration basics before we deep dive in each section in later articles.In VMware virtualization, we can perform multiple types of migrations of virtual machines.

VMware Virtual machine migration means moving a virtual machine from one host, datastore, or vCenter Server to another host, datastore, or vCenter Server.  We perform these activities  for Workload balancing, or as part of preparations to avoid downtime during activities like server maintenance, site level switch-over and other

Below are the types of migrations we can perform:

Cold:

Migration of a powered-off virtual machine from current host/datastore or both to a new host or datastore. Virtual machines can be migrated across vCenter Server in this type.

Suspended:

Migration of a suspended state virtual machine from current host/datastore or both to a new host or datastore. Virtual machines can be migrated across vCenter Server in this type.

vMotion:

Migration of a powered-on virtual machine from current host to a new host without downtime and zero data and connectivity loss.

Only the CPU and Memory instances on ESXi host gets migrated, virtual machine files on datastore are not migrated.

Virtual machines can be migrated across vCenter Server in this type.

Image: VMware

Storage vMotion:

Migration of a powered-on virtual machine’s files from current datastore to a new datastore.

In this type ESXi host is not changed, only datastore file location is changed from current datastore to new datastore.

Virtual machines can be migrated across vCenter Server in this type.

Image: VMware

Shared-nothing vSphere vMotion:

Migrate a powered-on virtual machine from current host and datastore to a new host and a new datastore as we are not using shared datastore here instead local datastore’s.

Image: VMware

Virtual machines can be migrated across vCenter Server in this type.

This migration type is often termed as vMotion+Storage vMotion due to its nature.

Image: VMware

NOTE: In case of vMotion, Shared nothing vMotion and Suspended state migration, CPU compatibility is must. CPU vendor and processor family should match, factors like number of cores, clock speed does not make any condition here.

Further reading, PART II and PARTIII

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.