![]() ![]()
When LM un-pauses on the destination host, the VM can instantly connect to the LUN and continue IO uninterrupted. During Live Migration the new instance of the VM on the destination host is set up with WWN B. So in this below example, the VM is connecting to storage using WWN A. With FC, we need to ensure that the VM is able to connect and process IO. The switchover process is that the VM is paused on A and started on B. It is running on HostA and waiting to start on HostB. There is a very brief period where a VM exists on two hosts during live migration. Each virtual HBA in your VM must have 2 WWNs (either automatically created or manually defined), not just one. There’s a little bit of trickery involved here. So how does a VM that is connected to a FC SAN move from one host to another without breaking the IO stream from VM to storage? One of the key themes of Hyper-V is “no new features that prevent Live Migration”. Now you have true SAN path fault tolerance at the physical, host, and virtual levels. #THE VIRTUALIZATION INFRASTRUCTURE DRIVER VID IS NOT RUNNING SERVER 2012 SOFTWARE#In fact, you can (and should) use your storage vendor’s MPIO/DSM software in the VM’s guest OS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |