1

I am currently tasked with evaluating VSphere and VCenter server. I read about the VMotion feature:

http://www.vmware.com/files/pdf/VMware-VMotion-DS-EN.pdf

This could come in very handy for us. We are always migrating VM's in our current infra. My question is, how well do these "no downtime" migrations work when it comes to databases such as served with MySQL? Do they truly migrate without issue? I can't seem to find much information one way or the other.

  • Do they truly migrate without issue? - Please expound on the specific "issues" you're referring to and concerned with. – joeqwerty Sep 17 '15 at 21:32
  • Will the database stop responding during migration, will there be data loss, queued connections, etc.. – Jafo Sep 17 '15 at 21:36
  • 3
    It works great. This is a core and key feature of VMware and vMotion. – ewwhite Sep 17 '15 at 21:37
  • Live migration works fine for smaller databases, but becomes problematic for larger databases or databases. Can you imagine live-migrating 4TB worth of data? Even the deltas could be quite large. It can work, and people do it, but you'll need to put a lot of thought into the architecture. Most other shops seem to use another form of HA. – Stefan Lasiewski Sep 17 '15 at 21:54
  • 1
    It think it should be important to know which feature you are realy talking about: vMotion is just moving the vm from one host to another - in fact it is just moving the content of ram. Storage vMotion is moving the vm files from one datastore to anoter. – Tobias Sep 21 '15 at 9:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.