Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
Hi, I'm Edwin Yuen, a Senior Technical Product Manager at Microsoft's Integrated Virtualization team. In today's blog, I'd like to discuss another type of migration being added to System Center Virtual Machine Manager 2008 R2, Quick Storage Migration.
Quick Storage Migration (QSM) In Brief
As you may have seen, we recently released the Release Candidate for System Center Virtual Machine Manager 2008 R2. One of the most anticipated features of SCVMM 2008 R2 is Quick Storage Migration (QSM) which enables the migration of the storage of VM from one location to another. For example, suppose you have virtual machines on a leased SAN (SAN 1). The lease runs out and you decide to upgrade to a new SAN (SAN 2) with more capacity, better performance and additional capabilities. Quick Storage Migration allows you to move the virtual machine which resides on SAN 1 to SAN 2. I have had a number of request for more details on how this works so we've written this brief guide to QSM. (In addition, we wanted to make this technology broadly available, not just the biggest enterprises. More on that below.)
QSM relies on Windows Server 2008 R2 Hyper-V and Background Intelligent Transfer Service (BITS). QSM can move the virtual disks of a running virtual machine independent of storage protocols (iSCSI, FC) or storage type (local, DAS, SAN), with minimal downtime.
QSM Is One of Many Migration Technologies Supported in Virtual Machine Manager's Portfolio
VM Migration Type
Platforms available on
Technology used for transfer
Expected downtime for VM
Under 1 minute in most cases
Network based migration
(aka LAN migration)
Minutes to hours (W2K8, W2K3 hosts)
Under 1 minute in most cases (W2K8 R2)
Storage Migration Type
Quick Storage Migration
Note on Processor Compatibility Mode:
To increase the mobility of a running virtual machine across hosts with different processor versions (with in the same processor family), Windows Server 2008 R2 Hyper-V offers Processor Compatibility Mode. This feature masks processor feature differences between the source and destination hosts. With this enabled, you can migrate a virtual machine from a host with Pentium 4 VT processors to a host with Nehalem processors. Processor Compatibility Mode does not require advanced processor features like Intel VT Flex Migration or AMD-V Extended Migration. For more on Processor Compatibility Mode, check out Jeff's Blog a few weeks ago where he goes into detail here.
How QSM Works
QSM uses native Windows platform technologies: Hyper-V and BITS. There are 2 scenarios of interest:
Scenario 1: VM Storage Migration: VM Compute Stays on the Same Server and the VM Storage Migrates from One Storage to Another
1. In the SCVMM console, a new action labeled Storage Migration is now available.
2. When the user right-clicks on a running virtual machine and selects the Migrate Storage action, a wizard is presented. The user provides the path to the new location to be used by the VM. If all the VMs files (configuration and VHD files) are to be placed in a single location the user has only to provide the "Virtual Machine Path". If one or more VHD files for the VM need to be placed at a separate location, the user can explicitly change the location of each VHD by selecting it from the list under "Disks" and clicking the "Browse" button next to it to specify the path for the VHD.
3. SCVMM takes a Hyper-V snapshot of the running virtual machine. This will create a differencing disk for each VHD connected to the VM. All disk write operations from that point forward go into the differencing disk. The original base VHD is no longer changing since it is in a read-only state.
4. With the base VHD in a read-only state, SCVMM starts to transfer the file from the source location to the target location using BITS. This represents the bulk of the data that needs to be transferred and the VM remains running during this transfer. In addition, QSM does not depend on storage types, and the user is free to select any storage destination that is accessible to the Hyper-V host.
5. Once the base VHD is transferred, the virtual machine is put into "Saved State".
6. In "Saved State", SCVMM can transfer the differencing disk created by the snapshot and memory associated with the "Saved State" to the destination location for the VM.
7. Once all the files are transferred, SCVMM exports and then re-imports the virtual machine on the same Hyper-V host with any necessary modifications to the configuration.
8. The snapshot created on step 3 is merged back into the base VHDs
9. Virtual machine is re-started from saved state
10. Job completes
11. The diagram below illustrates the steps performed by QSM on a Hyper-V R2 host.
Scenario 2: VM Migration (Relocation): VM Compute Moves to a News Server AND VM Storage Moves from One Storage to Another
1. In the SCVMM console, the user right-clicks on a running virtual machine and selects the Migrate action, a wizard is presented to help with the migration. The Migrate action initiates the migration of a VM from one host to another host. As part of the VM migration, all of the VMs files are moved to storage that is attached to the destination host. Storage Migration technology enhances the experience by allowing the move for a running virtual machine and limiting the down time of the VM to just the window required to move the save state files (as explained below).
2. The user first selects the destination host based on the desired star rating presented by Intelligent Placement. The user then provides a destination folder for the configuration file and the associated virtual disks. By default, the wizard will put all disks in the same location as the configuration file. After completing the wizard, the migration job is submitted.
3. SCVMM creates a placeholder virtual machine on the destination host. The virtual machine is not powered on so there is no need to reserve CPU or memory resources at this time. Intelligent placement has already accounted for the impact on the destination host of the VM being migrated.
4. SCVMM takes a Hyper-V snapshot of the running virtual machine. This will create a differencing disk for each VHD connected to the VM. All disk write operations from that point forward go into the differencing disk. The original base VHD is no longer changing since it is in a read-only state.
5. With the base VHD in a read-only state, SCVMM starts to transfer the file from the storage location on the source host to a storage location on the target host using BITS. Since QSM does not depend on storage protocols or storage types, the user is free to select any storage destination as long as the Hyper-V can access it.
6. Once the base VHDs are transferred, the virtual machine is put into Saved State.In Saved State, SCVMM can transfer the differencing disks created by the snapshot and associated memory state.
7. Once all the files are transferred, SCVMM exports the virtual machine and transfers the exported virtual machine configuration to the target host and then imports the virtual machine to Hyper-V host with any necessary modifications to the configuration.
8. The snapshots are merged back into the base VHDs as part of the import process.
9. Virtual machine is started from saved state
10. Job completes
How QSM Compares To VMware Storage VMotion
VMM 2008 R2 + Windows Server 2008 R2 Hyper-V
VMware (vCenter 2.5 + ESX 3.5)
Migration of virtual machines across two hosts with independent storage
Migration of virtual machines with snapshots
Migration of Virtual machine with Virtual Disks
Supported (persistent mode)
Requires sufficient resources to support two instances of the virtual machines running concurrently
Additional Licensed Required
Number of concurrent storage Migrations allowed
Storage Migrations supported in the Administrator Console
Yes (QSM and Storage vMotion)
Storage Migrations supported in the CLI
Support for migrations of VMs and storage between hosts with different processors versions (same manufacturer)
Yes (use Hyper-V R2 Processor Compatibility Mode to increase the number of compatible hosts )
Microsoft: Driving Down Costs
One thing our customers have been telling us loud and clear is that they are very, very happy we are offering Live Migration for FREE with Hyper-V R2. With Quick Storage Migration, we knew we had another opportunity to drive down the costs for storage migration capability that has been largely priced out of the reach of most customers. Specifically, VMware Storage VMotion is only available in their Enterprise/Enterprise Plus SKUs ($2875 & $3495 per processor respectively). Contrast this with the fact that Quick Storage Migration is included with System Center Virtual Machine Manager 2008 R2 both the Enterprise Edition and the Workgroup Edition which will be available for starting at about $500.
For a small five node cluster consisting of two and four processors servers, that would cost at a minimum:
Virtual Machine R2 QSM
That's customer focus.
Sr. Technical Product Manager
PingBack from http://up2v.wordpress.com/2009/06/25/quick-storage-migration-explained/
Below is written from the context of a current and long-time Microsoft customer and admin.
I think it would be great if this blog would take a turn to a more technical focus instead of all the marketing I see here lately. A little bit of trumpeting about your nifty features is great, sure, but most of these comparisons with VMWare are inaccurate, reflect older versions, or simply don't mention details that will matter once implementation time comes. Storage vMotion for instance now works across disparate and non-shared storage. What about the network features? What about the richness of support for other Operating Systems?
I think it's great (who wouldn't?) that you will be offering live migration for free in the near future. To describe that as less than a panacea would be a shame. But, to describe this as customer focus is a mockery when it is obviously just a simple sniping attempt from your greatest competition. No doubt it will be quite successful in the SMB market.
I also found the running tabloid of marketing misadventures with the Hyper-V BSOD video to be rather amusing when MS marketing has engaged in similar tactics over and over again for decades. Just because you don't do it now doesn't mean it never happened and the way this blog has been lately is treading a thin line. Why ruin the good name that MS has managed to partially claw back over the last 5-10 years? Start focusing on you and not them; this banter is tiring!
Common Hyper-V guys: lets hear more tech and less FUD here! Would be great to see stories about the challenges of working across two different cpu vendors or the intricacies of Live migration over Ethernet or other things that are actually interesting.
Try to keep in mind that you're the one playing catch-up in this market. A little humility never hurt anyone. :)
and picture the person who made the table was beautiful expression of the hands of health
Attempting to use "storage migration" however it appears I am getting very poor bit peformance. Any suggestions on how to improve BITS performance when copying? I remember in the SCVMM 2k8 TAP we were recommending that customers disable TCP Offloading and some other settings on the card (BroadCom NetFX II)...thanks.
Why you are compairing with ESX3.5, compair with ESX 4.x. Then actual figure comes out, other wise above comparison is falls.
Agree with Ajay - your comparison towards the end of the blog post is incorrect. Your table compares with ESX3.5, however you mention licensing with Enterprise/Enterprise Plus. If you are comparing with ESXi4.1, this table would look very different.
otomatik kapılar, otomatik kepenkler, fotoselli kapılar, garaj kapıları, motorlu panjurlar
I have this scenario:
Two Hyper-v servers R2 SP1 with shared iSCSI storage on a SAN IBM DS3500. One is running 3 machines as standalone, and the othe brand new node is actually not running any machine. I would like to set up a Hyper-V cluster with both hosts with the minimum impact on the guests availability.
I have SCVMM Essentials installed on a third host.
Could I set up a one node Hyper-V cluster and then migrate all the machines, after that join to the cluster the second node?