A vMotion migration gives you the ability to perform live migrations with zero downtime. A vMotion migration proactively moves virtual machines away from failing or under-performing servers. It continuously and automatically optimizes virtual machines within resource pools, and performs hardware maintenance without scheduling downtime and disrupting business operations.
What causes of a vMotion migration?
Hardware failure on a host machine can cause a vMotion migration: after hardware fails, the vMotion process begins. During this period, connectivity might be momentarily lost while a slice is moved to a healthy host. Hardware failures can be caused by power loss, memory failure, CPU failure, or NIC failure.
Do host reboots require an instance reboot?
Occasionally. In the event of a host failure, Engine Yard on Terremark features are designed to minimize risk of downtime by automatically migrating instances to healthy nodes with little to no interruption. However, sometimes there are problems during the migration and instances need to be rebooted.
What do I need to do if my instance requires a reboot?
Instances that are rebooted might need to have key services restarted and rejoined into the cluster. If this occurs, you can either update a related ticket or open a new one for assistance from Engine Yard Support.
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.