Sign in
Home
Library
Wiki
Learn
Gallery
Downloads
Support
Forums
Blogs
Resources For IT Professionals
United States (English)
Россия (Pусский)
中国(简体中文)
Brasil (Português)
Post an article
Translate this page
Powered by
Microsoft® Translator
Wikis - Page Details
First published by
KristianCloud
(Microsoft Partner)
When:
6 Apr 2011 6:33 AM
Last revision by
Leandro E. Carvalho
(MVP, Microsoft Partner)
When:
6 Apr 2011 8:05 PM
Revisions:
2
Comments:
0
Options
Subscribe to Article (RSS)
Share this
Can You Improve This Article?
Positively!
Click Sign In to add the tip, solution, correction or comment that will help other users.
Report inappropriate content using
these instructions
.
Wiki
>
TechNet Articles
>
Live Migration process in Windows Server 2008 R2
Live Migration process in Windows Server 2008 R2
Article
History
Live Migration process in Windows Server 2008 R2
- Windows Server 2008 R2 support a feature called ‘Live Migration’
Yes it does, but there are some requirements you need to meet before you are able to live migrate your VMs.
Let us take a quick look at the requirements:
·
Windows Server 2008 R2 Enterprise/Datacenter (You can also use the Microsoft Hyper-V Server 2008 R2)
·
Failover Cluster feature installed on every node that will use live migration (supports up to 16 nodes per cluster)
·
Use dedicated network for live migration
·
The nodes in the cluster must use a processor from the same manufacturer
·
The nodes must be on the same subnet
·
Access to shared storage
·
Clustered Shared Volume enabled (CSV)
·
Identical names on the Virtual Networks in Hyper-V
The Live Migration Process:
What happens when you initiate a live migration from node 1 to node 2 in Failover Cluster Manager ?
1.
The source node makes a
connection (TCP)
with the destination node to transfer the VM configuration data. A ‘copy’ of the VM is created on node 2 and memory is allocated.
2.
Memory is transferred
from source node to destination node. The memory copies over the network, and the migrating VM continues to run.
3.
A final memory copy process
copies the remaining modified memory pages to the destination node. In this stage the network between source and destination is critical to the speed of the live migration. (1GB is recommended) Also, if the VM is heavily accessed under the live migration, that might affect the speed as well.
4.
Move the ‘storage’ from source node to destination node
(.vhd files, pass-through disks)
5.
The VM is online on the destination node
since it now has the updated working set and access to the VM storage.
6.
Time to cleanup!
A message is sent to the physical network switch telling him to re-learn the MAC address of the migrated VM. Now the VM can use the correct switch port.
The benefits this feature gives us, is that it provides us with the opportunity to build a dynamic datacenter, easier maintenance of the nodes, and a hot topic in these days:
green IT
cloud
,
Failover Clustering
,
Hyper-V
,
Kristian Nese
,
Live Migration
,
Requirements
,
Virtualization
,
Windows Server