Microsoft VMM2008 actual combat P2V migration strategy

VMM2008 allows the administrator to transform the physical host that exists in the production environment to the Hyper-V virtual machine, which is often referred to as production to virtual conversion. Also known as P2V. The Migration (Transformation) wizard through the VMM Management console makes it easy to implement P2V.

I. VMM and P2V INTRODUCTION

VMM 2008 can also transform virtual machines on other virtualized platforms. For example, the virtual machine on VMware ESX and Microsoft Virtual SERVER R2 is converted to Hyper-V on Windows. Which is often called the V2V.

In general, there are two ways to implement P2V, one of which is to replicate the online conversion of data by using the Volume Shadow copy technology (VSS Volume Shadow copy Service) of Windows, which does not affect requests that serve the user at the same time as the source physical host is converted to a virtual machine. The other is offline (offline) by restarting the source physical host in the WINDWS PE environment and transforming the physical disk into a virtual hard disk (VHDs) by VMM.

The operating systems supported in the P2V transformation are listed below: (Figure 1)

Both online and offline (offline) P2V conversions, VMM 2008 will temporarily install agents on the source physical host to help with the conversion.

Note: VMM 2008 does not support the P2V conversion of the source physical host OS as Windows NT4.0, but can be migrated using Microsoft Virtual Server Migration Tookit (VSM) or third-party solutions.

Second, the P2V conversion of the environmental requirements:

To achieve P2V conversion, the source physical host must meet the following requirements:

1, the domain environment: the source physical host needs and VMM2008 in the same domain or two-way trust domain.

2, Memory: Offline (offline) P2V conversion requires a source physical host at least 512M of memory.

3. Update: Large P2V conversions are not affected by updates, however, some system files and drivers are reset during the conversion process and may need to be updated after the conversion is complete. If these files are missing, the administrator must add them to the path to import VMM.

Iii. some instructions or preparations before the P2V conversion process

When you run the transformation, the VMM administrator needs to provide an account and password with administrator privileges on the source physical host. At the same time, it is a good idea to scan the source physical host for disk fragmentation and provide a fast network connection (such as a gigabit network environment) before executing the procedure.

1, P2V implementation of the network topology (Figure 2)

Due to the conditions, I put domain controllers, domain members (physical hosts to be converted) and SCVMM Management Console (VMM server) on a single VMware 6.5 installed on the XP SP3, while installing a stand-alone Windows Server 2008 Hyper-V The goal of this P2V conversion is to convert Vista online to Hyper-V.

2, SCVMM Management Console (Figure 3)

As shown in the figure, this is the administrative console for the installed SCVMM, and all operations can be done in the Operations Wizard provided by this management console. The P2V operation we do is to "transform the physical server" in the right-hand panel.

3, in the "transformation of physical server" operation, we first to add the operation of the host, otherwise, the source physical host can not be converted into a virtual machine. Because the previous article has been explained to add a host. Here only the finished diagram is posted: (Figure 4)

You can see that the computer name for Windows 2008 with Hyper-V is: hyper-v.contoso.com. It will be used in the P2V, while the hypervserver in the figure is the independent Hyper-V Server 2008 that is added later, which can be ignored.