VMware vMotion support
With a VMware vSphere setup with multiple ESX servers managed by a vCenter Server, the vMotion feature can be used to migrate live guests running as an System Automation for Multiplatforms node. The migration does not affect the state or operation of the System Automation for Multiplatforms cluster, provided that the cluster is configured to use standard (that is, default) heartbeat settings. In that case, the effect on the application servers running under System Automation for Multiplatforms control is a brief interruption of operations during the migration. Neither System Automation for Multiplatforms nor the application servers will have to be restarted.
Make sure that the period of interruption during vMotion does not cause unwanted cluster events. Unwanted cluster events will occur if too many heartbeats from the node are missed during the average period of interruption. In that case, relax the heartbeat settings for the time of vMotion.
Another way to minimize the chance of unwanted cluster events while an virtual guest is moved is
to stop the peer domain forcefully before the move is initiated with stoprpdomain
-f, that is, without stopping the applications managed by the cluster services. After the
move is completed, restart the peer domain.
- SLES 12 or 15 (x86-64)
- RHEL 7 or 8 (x86-64)
- Ubuntu 18.04 or 20.04 (x86-64)
Limitations: System Automation for Multiplatforms does not support vMotion of nodes that use shared storage, because vMotion does not support shared real or virtual storage volumes (disks).