Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:vmotion [2023/03/05 09:22] – created bstafford
+++ infoblox_nios:vmotion [2024/03/28 17:02] (current) – bstafford
@@ Line 1: / Line 1: @@
 ====== NIOS VMotion ======
-If you have to move a VM from one cluster to another cluster (not VMotion, but power off and copy over files), make sure you snapshot before powering on and then tick "I moved it" when asked if you moved or copied it). If it all works, remove the snapshot as quickly as possible. The main issue is that if the VM boots and the UUID changes, the licenses immediately break. This is why you take the snapshot.
+[[https://docs.infoblox.com/space/NVIG/35786270/Migrating+NIOS+Virtual+Appliances|vMotion—Hot]] and Cold VMware vMotion migrations are supported. However, Cold migrations can result in a change in HWID and MAC Address, which invalidates the licensing. When this occurs, the licenses will need to be regenerated based on the new appliance details.
+Cold V-motion is not recommended by Infoblox. Cold vMotion occurs when a vNIOS appliance is shutdown during vMotion. Performing Cold vMotion on a vNIOS appliance resets the Hardware ID and MAC address of the Virtual network interfaces of the VMWare ESXI servers.  Rather that using Cold vMotion, use Hot vMotion on vNIOS hosts. Hot vMotion occurs when the vNIOS appliance is not shut down. Hot vMotion preserves the Hardware ID and MAC address of the virtual network interfaces. As a result, the licenses are not affected.
+Note articles [[https://support.infoblox.com/s/article/2963|here]] and [[https://support.infoblox.com/s/article/11316|here]] and [[https://kb.vmware.com/s/article/1541|VMware article here]]
+VMware Snapshots are discouraged as we have seen issues with appliances rebooting when using this feature. Instead, we recommend the use of Scheduled Backups within NIOS
+If you have to move a VM from one cluster to another cluster (not VMotion, but power off and copy over files), make sure there are no VM snapshots before the move. After the move and before powering on the VM, take a snapshot. VMware should ask you if you copied it or moved it. Tick "I moved it" when asked (this keeps the UUID instead of creating a new on). If it all works, power off the VM and remove the snapshot as quickly as possible. The main issue is that if the VM boots and the UUID changes, the licenses immediately break. This is why you take the snapshot.
 A better way is to deploy new VM's and then move the licenses over in the support portal.