Balancing Resource Utilization

  • Verify the following vMotion requirements are met.
    • Shared storage for the VM files (a VMFS or NFS datastore) that is accessible by both the source and target ESXi host.
    • A Gigabit Ethernet or faster network interface card (NIC) with a VMkernel port defined and enabled for vMotion on each ESXi host.
    • Processors in both ESXi hosts must be compatible.
      • CPUs must be from the same vendor.
      • CPUs must be from the same CPU family.
      • CPUs must support the same features, such as the presence of SSE2, SSE3, and SSE4 and NX or XD.
      • For 64-bit VMs, CPUs must have virtualization technology enabled (Intel VT or VMD-v).
    • The VM must not be connected to any device physically available to only one ESXi host.
    • The VM must not be connected to an internal-only virtual switch.
    • The VM must not have its CPU affinity set to a specific CPU.
    • The VM must have all disk, configuration, log, and NVRAM files stored on a VMFS or NFS datastore accessible from both the source and the destination ESXi hosts.
  • Enable VMware Enhanced vMotion Compatibility (EVC).
  • Verify the following cross vCenter vMotion requirements are met.
    • Both vCenters involved in the migration must be a minimum of vCenter 6.0.
    • Participating vCenter Servers must share a Platform Services Controller (also known as enhanced linked mode).
    • All hosts must be at lease vSphere 6.0.
    • The RTT between hosts must be less than 100ms.
  • Enable and Configure vSphere DRS.
    • Automation Level: Fully Automated.
    • Migration Threshold: 3.
    • Verify the task completed in the Recent Tasks pane.
    • Create any VM Affinity Rules, VM Anti-Affinity Rules, or Host Affinity Rules.
    • Configure any VM Overrides.
  • Enable Storage DRS.
    • Cluster Automation Level: Fully Automated.
    • Space Balance Automation Level: Fully Automated.
    • I/O Balance Automation Level: Fully Automated.
    • Space Threshold: 90%.
    • Configure any custom SDRS schedules.
    • Create any VMDK Affinity Rules, VMDK Anti-Affinity Rules, or VM Anti-Affinity Rules.