This article will let you know about vMotion, prerequisites, procedure of vMotion and detail of Affinity rule.
Migrating VM’s from source system to destination system. vMotion used to move running VMs of one ESXi server to another. Only CPU and Memory resources processing is actually moving from one to another host without any downtime and the disks will stay in the same datastore (not in Storage vMotion) where it is now. Only 1 or 2 ping packets may lose during vMotion if you are pining in continuous mode.
Use of vMotion:
- Load balancing:- Using DRS, when VM’s needs more resources, VM’s moved to another ESXi host.
- Using DPM:- Evacuating all the VM’s servers to an underutilized host and power off the previous host. Distributed power management whenever the resources utilization increases, DPM distribute the VM’s to the previous ESXi host power back on without any applications downtime, users working on the applications doesn’t even know.
- Hardware Maintenance and patching using update manager
- vSwitch with zero uplink adapter: Means VM’s must not have any internal connection with standard vSwitch.
- VM’s must not have local image mounted on virtual devices.
- VM’s must not have affinity rule configured.
- CPU compatibility checks if using EVC.
- VMKernal must be enabled with vMotion for both the ESXi hosts.
- vSphere licenses like enterprise plus, essential plus, standard enterprise.
- Swapfile must be accessible to the destination host if it is not accessible then vMotion must be able to create swapfile accessible to the destination host before migration can begain.
- If any VM uses RDM then it must be accessible by the destination host.
- Shared storage between ESXi hosts
- Identical port groups connected with the same physical network having same name.
- At least a GB Ethernet network:-A). 8 concurrent vMotion migrations on 10 Gbps N/W. B) 4 concurrent vMotion migrations on 1 Gbps N/W.