
Section 14 Improving Availability VMware vMotion
3BSE056141-510 F 135
VMware vMotion
VMware vMotion is the ability to move virtual machines from one ESX(i) server to
another while it is running. It is required that the ESX(i) servers are members of a
vCenter server and that the virtual machines are stored on a SAN server.
When a vMotion operation is performed, the memory of the virtual machine is
progressively transferred to the other ESX(i) server. Changes in the memory of the
original virtual machine are tracked and transferred. When the remaining memory to
be transferred is small enough to be performed in one last operation, the virtual
machine is stopped, the remaining memory transferred, and the virtual machine
execution is continued on the other server. This generally results in a loss of one
ping on the network. Depending on the network speed and the CPU activity of the
virtual machine, this time may be more or less.
It is important to keep in mind that while the loss of network connection may be in
the order of a few seconds, applications and services on the computer transferred, or
communicating with the computer transferred may take longer to return to normal
operations.
To assist in minimizing interference with the storage network communication, a
separate network should be used for vMotion operations.
VMware Storage vMotion
VMware Storage vMotion is not supported for System 800xA.
VMware Fault Tolerance
VMware Fault Tolerance is not supported for System 800xA.
VMware vMotion must not be used during production, only for maintenance
operations during a maintenance stop of the factory.
Kommentare zu diesen Handbüchern