Encrypted VMs always migrate this way; for others it is a per-VM choice of Required, Opportunistic or Disabled. Encrypting the vMotion data keeps it confidential and guards its integrity and authenticity.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Encrypted vSphere vMotion in context, with comparison tables and the common traps.
Terms in this definition
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- Migrate
Part of Adopt in the Cloud Adoption Framework: the guidance for lifting workloads you already run, on-premises or in another cloud, across to Azure. It assumes you have prepared a migration adoption plan and built a landing zone. Not to be mixed up with the Azure Migrate service.
- DISABLED
A plan mode that still allows editing, testing and scanning, but turns off scheduled runs and automatic report refreshes.
- vMotion
Moves a running VM to another host with no downtime; its storage counterpart, Storage vMotion, relocates the files between datastores instead.
- Integrity
One leg of the CIA triad: information remains correct and is only changed through approved means. Hashes, digital signatures and audit trails help guard it.