Detailed live migration of Windows Server 2012 without shared storage

Windows Server no need for shared storage real-time

Microsoft has provided its latest virtualization platform in Windows Server (WS2012)-Hyper-V 3.0, relying on WS2012 's latest SMB (Server Message Block) protocol for transparent migrations, which we often call live migrations, This means that we are able to migrate without disrupting the VM's operation. Although this technology can be achieved before, but we need to pay a high cost, in the past in order to achieve migration we have to purchase dedicated shared storage devices, and now Windows Server 2012 in the virtual machine mobility has made a significant improvement. We no longer have to rely on shared storage devices for real-time migrations.

Windows Server 2012 also gives us a very resilient and flexible choice, relying on the four real-time migration scenarios that Windows Server 2012 currently implements:

• Live migration without shared storage

• Live migration with SMB shared storage

• Migration in a storage environment

• Live migration in a failover cluster

And today Goxia will lead you to practice without sharing storage of real-time migration, I believe you will have a small harvest. As the name implies, live migrations without shared storage enable us to move their virtual machines directly between Hyper-V hosts of multiple domain members without disrupting the running VMS.

650) this.width=650; "width=" 634 "height=" 272 "title=" shared_nothing_live_migration "style=" border-width:0px; Padding-top:0px;padding-right:0px;padding-left:0px;background-image:none; "alt=" Shared_nothing_live_migration " Src= "Http://goxia.maytide.net/ftpupfiles/WS2012-Windows-Server-2012-_7DE4/shared_nothing_live_migration_ Thumb.png "border=" 0 "/>

The basic process of doing this is to use SMB to implement live migration of files such as virtual machine VHDs, synchronize migrated virtual machine VHD file images and snapshots to target host (Hyper-V), while the migration process's connection management relies on VMMS (virtual machines Management Service). After the files such as VHDs are synchronized on both ends, the next steps of the live migration are started, first the virtual machine's state information is migrated from the source host to the target host, then the synchronization relationship between the two files is interrupted, the file storage on the source host is deleted, and the migration connection is completed.

Live migrations without shared storage also have the following four features:

• Even if a failure or problem is encountered in the migration project, resulting in a migration failure, there is always a guaranteed virtual machine available.

• VMS can be migrated across clusters, for example, we can migrate from a non-clustered computer to a clustered computer.

• Migrate virtual machines that support different storage types without the need for storage type constraints, enabling real-time migrations regardless of whether the environment is JBOD or direct storage, or ISCSI storage.

• You can use Powershell to initiate an operation that implements the migration, so you can automate the operation.

In summary, live migration without shared storage provides us with a low-cost, high-efficiency, flexible and easy-to-use migration solution that allows us to apply this feature to a wide range of application environments. For example:

• The development or IT staff can migrate the tested virtual machines directly to the production environment without any downtime.

• In a multi-host environment, if you need to perform host maintenance, you can quickly and flexibly move virtual machines between hosts without relying on shared storage.

• Troubleshooting and hardware upgrades, SMBs may have only one server and run a business Server in a virtualized way, and it consultants can quickly build a temporary Windows server 2012-based Hyper-V host on a notebook when a hardware failure occurs or a server needs to be updated. Add it to the existing domain to complete the migration of the business VM, after the replacement of the original server, and then migrate back.

With real-time migration technologies that do not require shared storage, which can be used in many scenarios, the next Goxia will lead you through a hands-on walkthrough, with two Windows Server 2012-based Hyper-V hosts ready and joined to an existing Active Directory (AD domain). This step is necessary. Then, create a virtual machine on one of the hosts for the migration practice. Take the Goxia environment for example, use two devices: Dell T310 (Intel Xeon X3470), Thinkpad T420 (Intel i7-2620m), install WS2012 enable Hyper-V, and add to the company Active Directory (AD domain), create an XP virtual machine on HV3, the LAN is a gigabit network.

650) this.width=650; "Width=" 630 "height=" 228 "title=" image "style=" border-width:0px;padding-top:0px;padding-right : 0px;padding-left:0px;background-image:none; "alt=" image "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/image_thumb.png "border=" 0 "/>

When you are ready, you first need to configure two virtual machines, enable the migration feature, open Hyper-V Manager for this, select the host to operate, click the right mouse button select "Settings", in the "Implement migration" option check "Enable incoming and outgoing live migration", authentication protocol Select "Use Kerberos" , the parallel live migration setting remains the default because it is a test, so an incoming live migration can choose to use any available network for live migration.

650) this.width=650; "width=" 634 "height=" 358 "title=" 2 "style=" border-width:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 2 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/2_thumb.png "border=" 0 "/>

With these settings, we can start the migration process, and a friend may ask, "Why didn't you follow the other tutorials on the web to do delegation of authority?" Wouldn't it be a migration failure?! "Is that the case?! Goxia will share this knowledge with you at the end of the article! Start with our migration step, first log on to the Hyper-V host where the XP virtual machine is located (HV3), open Hyper-V Manager to select the XP virtual machine, and on the right "action" form click on "Move ..." to start the Migration Wizard and click "Next" on the first page of the wizard.

650) this.width=650; "width=" 628 "height=" 474 "title=" 3 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 3 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/3_thumb.png "border=" 0 "/>

In the Specify Destination Computer Wizard page, in the Name box, type the target host name for the virtual machine migration, which is hyper-V and, of course, you can confirm the selection by browsing.

650) this.width=650; "width=" 628 "height=" 474 "title=" 4 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 4 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/4_thumb.png "border=" 0 "/>

Under Move options, select Move data from virtual machine to a location by default and click Next. If you want to store a profile, paging file, or snapshot to a different location on the destination host, you can choose to move the data for the virtual machine by selecting the project move location, and the move virtual machine only applies to environments that use SMB shared storage.

650) this.width=650; "width=" 628 "height=" 474 "title=" 5 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 5 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/5_thumb.png "border=" 0 "/>

The resource management form for the target host is then ejected, allowing us to select and determine where the target is stored.

650) this.width=650; "width=" 634 "height=" 358 "title=" 6 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 6 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/6_thumb.png "border=" 0 "/>

Complete the above steps close to half the success, confirm each option setting and click "Finish" to start the migration, as shown in:

650) this.width=650; "width=" 628 "height=" 474 "title=" 7 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 7 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/7_thumb.png "border=" 0 "/>

The next procedure will be error (PS: not permission delegation error, everybody don't worry!) ), "Cannot move the virtual machine to the destination computer." The hardware on the target computer is incompatible with the hardware requirements of this virtual machine, "the specific prompt says:" The virtual machine is using a processor-specific feature that is not supported on Hyper-V on the physical computer. "Looking back at the previous text, whether to notice the goxia of the practical environment of the computer processor has been marked with eye-catching!" Microsoft virtualization Real-time migration technology does not currently support virtual machine migration between processors in different vendors. However, real-time migrations with different processor versions of vendors are supported. Therefore, the hardware compatibility errors mentioned earlier can be set on the VM configuration to resolve. To do this, check the virtual machine into its property settings, find the processor in the right form and expand the options to enter the compatibility setting, and check migrate to a physical computer with a different processor version. Once this is done, the processor compatibility issue can be resolved, and we may restart the migration operation.

650) this.width=650; "width=" 428 "height=" 359 "title=" 8 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 8 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/8_thumb.png "border=" 0 "/>

650) this.width=650; "width=" 634 "height=" 599 "title=" 9 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" 9 "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/9_thumb.png "border=" 0 "/>

We also encounter a problem during the migration process (PS: Don't worry, it's not permission delegation!) haha), the Migration Wizard may prompt us not to find the virtual machine's network connection on the target host, namely: "Virtual Switch". This is a common problem because we may not be planning the name of the virtual switch on all Hyper-V hosts, although it is not possible to verify that the virtual machine's network connection exists on the target host while migrating the configuration file, but the Migration Wizard provides us with steps to resolve the problem. You can re-specify the virtual machine on the target host already exist on the VM switch, that is, we often say that the virtual network card, although the re-specified settings, but the MAC address before the virtual machine will be retained, this is to ensure transparent migration premise!

650) this.width=650; "width=" 628 "height=" 474 "title=" "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=", "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/10_thumb.png "border=" 0 "/>

Finally confirm the migration options, click "Finish" and start the migration!

650) this.width=650; "width=" 628 "height=" 474 "title=" one "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=", "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/11_thumb.png "border=" 0 "/>

The amount of time spent in the entire migration process depends on the size of the VM being migrated and the network bandwidth and disk I/O performance of the server, and in the Gigabit network environment of Goxia, the migration based on SATA disks takes a few minutes to complete within a reasonable acceptance range! The whole migration process did not interrupt the operation of the virtual machine, in practice, Goxia Ping and network copies were tested, no exception occurred.

650) this.width=650, "width=" 634 "height=" 359 "title=" "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=", "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/14_thumb.png "border=" 0 "/>

Windows Server 2012 Live migration without shared storage overall is easy to use, without the need for too many complex setups, and a closer look at a few simple steps that rely entirely on a strong infrastructure as a support, so AD is a must!

Now let's talk about delegation of authority! On-line an article mentions that Windows Server 2012 Live migration without shared storage does not support bidirectional operations, simply by connecting the B host with Hyper-V Manager on a host and migrating the virtual machine of Host B to host A, which will certainly fail when the default is set! Because the Kerberos authentication protocol by default, the Hyper-V host only trusts the migration originating from the native, the simple understanding is that only the resources on its own host are actively moved to other hosts, the other is to delegate permissions! Otherwise, a common error like the ones shown will appear!

650) this.width=650; "Width=" 464 "height=" 413 "title=" 0x8009030E "style=" border:0px;padding-top:0px;padding-right:0 Px;padding-left:0px;background-image:none, "alt=" 0x8009030E "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/0x8009030e_thumb.png "border=" 0 "/>

"The virtual machine migration operation on the migration source failed" with the message "Unable to establish a connection to host Hyper-V: No credentials are available in the Security Pack (0x8009030E)." "When this error occurs, it must be that the user migrates the VM on host B through Hyper-V manager and does not have permission delegation set up. Therefore, in order to avoid such a situation, and in compliance with the premise of the Hyper-V host can set permissions for delegation. To do this, open ADUC locate the Hyper-V host, go to the Delegation tab of its properties, select Trust this computer only to delegate the specified service, select Use Kerberos only for the subkey, and add two service types "CIFS" and "Microsoft Virtual System Migration Service ", which represents SMB, the latter is the required VMMS service module. User or computer is set to the peer's host name.

650) this.width=650; "Width=" 495 "height=" 603 "title=" image "style=" border-width:0px;padding-top:0px;padding-right : 0px;padding-left:0px;background-image:none; "alt=" image "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/image_thumb_3.png "border=" 0 "/>

Once you have completed the above permission delegation settings, you can perform migration tasks (passive migration) on the current host to the operating peer or other host. Of course, there will be a netizen will ask "since the launch VM migration requires native trust, then the migration of the target host how to restrict or trust the source host to initiate the migration?! Simply said, which source hosts are allowed to migrate virtual machines to this machine?! In fact, the previous introduction to this question, that is: the Hyper-V host properties in the "Live Migration" settings under the "Incoming Live Migration" option, where we can specify which network or IP-initiated migration is accepted by this machine.

650) this.width=650; "width=" 444 "height=" 255 "title=" image "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://goxia.maytide.net/ftpupfiles/ Ws2012-windows-server-2012-_7de4/image_thumb_4.png "border=" 0 "/>

To ensure that live migrations without shared storage are performed smoothly, Goxia summarizes:

• The Hyper-V host must be a Windows Server 2012 system.

• The Hyper-V host must be joined to AD.

• The Hyper-V host processor (CPU) must be the same manufacturer, but allows a different version to be used.

• To perform a passive migration, you must configure permission delegation for the source host.

Ok! Come here to believe that you have a deep and correct understanding of the real-time migration of Windows Server 2012 without shared storage, and unlock the hearts of the doubt! Now interested in the Netizen can be right and smooth start to practice, wish June good luck!

Transferred from: http://goxia.maytide.net/read.php/1632.htm

In-depth live migration of Windows Server 2012 without shared storage