none
Hyper-V Migration RRS feed

  • Question

  • Hello All,

     

    We are planning to migrate our production server to Hyper-V. Is it recommended to use P2V migration for this scenario? How to have pass through discs created during migration?

     

    Appreciate your help.

     

    Thanks & regards,

    Ashish Basran


    Ashish
    Tuesday, February 2, 2010 4:16 PM

All replies

  • We cannot create pass through discs during P2V migration.
    Ashish
    Wednesday, February 16, 2011 10:25 PM
  • You could use System Center Virtual Machine Manager to P2V on your Server.
    Gustavo Faleiro Bastos MCSE|MCITP|CCNA|MCT Gfal Tecnologia at http://www.gfal.com.br
    Monday, February 21, 2011 9:03 PM
  • Does SCVMM gives option to create pass through disc during P2V?


    Ashish
    Tuesday, February 22, 2011 1:52 AM
  • You can use System Center Virtual Machine Manager Configuration Analyzer (VMMCA) to help you check the P2V source for some issues.

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=02d83950-c03d-454e-803b-96d1c1d5be24&displaylang=en

     

     


    Gustavo Faleiro Bastos MCSE|MCITP|CCNA|MCT Gfal Tecnologia at http://www.gfal.com.br
    Tuesday, February 22, 2011 2:55 AM
  • Agree, but it does not give option to create pass through discs.
    Ashish
    Tuesday, February 22, 2011 5:12 AM
  • Ashish,

    Changing a little bit the subject, but in the same question....

    Thinking in a safe manner, changes I make on my environments I always think in MOF or ITIL "Change Management" 1º - Test Environment, 2º - Pilot or Homolog and then 3º - take it to the production.

    In your case, if I was conducting, I give it a try before take to production, and then your question would be solved, and who knows other unexpected issues could be analyzed too, saving your production systems from stop.

    Thanks,


    Gustavo Faleiro Bastos MCSE|MCITP|CCNA|MCT Gfal Tecnologia at http://www.gfal.com.br
    Tuesday, February 22, 2011 11:21 AM
  • Gustavo: We first converted our POC then Development, Test, Preprod environments before converting our Production environment. For our servers we wanted to have pass-through discs created instead virtual discs. We could not achieve it using SCVMM-P2V wizard.
    Ashish
    Tuesday, February 22, 2011 4:52 PM
  • Is it recommended to use P2V migration for this scenario? How to have pass through discs created during migration?

    Hey Ashish,

    first of all for P2V for windows Machines u can use the SCVMM 2008R2 as for best practices please consider the following if u'r planning for an online migration;

    1. Stopping all Running Services such as SQL services or any services that has heavy Data Writing on the disks.
    2. after conversion there are some Cleanup u have to do;
    • Uninstall all HW Drivers that has been previously installed on the OS through the Physical Server.
    • Uninstall all Related HW Software applications like HP software related to networking.

    The requirements for physical source computers depend on whether you are performing an online or offline P2V.

    Online vs. Offline Conversions

    The following table lists some of the differences between the online and offline P2V conversions.

     

    Category

    Online P2V

    Offline P2V

    Source computer availability

    The source computer continues to perform normal operations during the conversion.

    The source computer is taken offline during the conversion.

    Process

    VMM creates a copy of local NTFS volumes and data of VSS-aware applications. VMM leverages the Volume Shadow Copy Service (VSS) to ensure that data is backed up consistently while the server continues to service user requests. VMM uses this read-only snapshot to create a VHD.

    The source computer restarts into the Windows Preinstallation Environment (Windows PE), and then VMM clones the volume to a VHD. Finally, VMM restarts the source computer into the original operating system.

    Compatibility

    Online P2V is the default for the operating systems on most physical computers.

    Offline P2V is the only option for Windows 2000 Server conversion, the only method to reliably migrate FAT volumes, and the recommended method for converting domain controllers.

    Advantages

    Source computer is available throughout the conversion.

    Offline P2V can be the most reliable way to ensure data consistency and is the only option in certain situations (see above).

     

    with both online and offline P2V, VMM temporarily installs an agent on the physical source computer to be converted. 

    Requirements on the Source Machine

    To perform a P2V conversion, your source computer:

    ·      Must have at least 512 MB of RAM.

    ·      Cannot have any volumes larger than 2040 GB.

    ·      Must have an Advanced Configuration and Power Interface (ACPI) BIOS – Vista WinPE will not install on a non-ACPI BIOS.

    ·      Must be accessible by VMM and by the host computer.

    ·      Cannot be in a perimeter network. A perimeter network, which is also known as a screened subnet, is a collection of devices and subnets placed between an intranet and the Internet to help protect the intranet from unauthorized Internet users. The source computer for a P2V conversion can be in any other network topology in which the VMM server can connect to the source machine to temporarily install an agent and can make Windows Management Instrumentation (WMI) calls to the source computer. 

    The following table lists the Windows operating systems for which P2V conversions are supported in VMM 2008 and in VMM 2008 R2.

    Supported Operating Systems for P2V Conversions in VMM 2008 and VMM 2008 R2

    Operating System

    VMM 2008

    VMM 2008 R2

    Microsoft Windows 2000 Server with Service Pack 4 (SP4) or later (offline P2V only)

    Yes

    Yes

    Microsoft Windows 2000 Advanced Server SP4 or later (offline P2V only)

    Yes

    Yes

    Windows XP Professional with Service Pack 2 (SP2) or later

    Yes

    Yes

    Windows XP 64-Bit Edition SP2 or later

    Yes

    Yes

    Windows Server 2003 Standard Edition (32-bit x86)

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 Enterprise Edition (32-bit x86)

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 Datacenter Edition (32-bit x86)

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 x64 Standard Edition

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 Enterprise x64 Edition

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 Datacenter x64 Edition

    Yes (Requires SP1 or later.)

    Yes (Requires SP2 or later.)

    Windows Server 2003 Web Edition

    Yes

    Yes

    Windows Small Business Server 2003

    Yes

    Yes

    Windows Vista with Service Pack 1 (SP1)

    Yes

    Yes

    64-bit edition of Windows Vista with Service Pack 1 (SP1)

    Yes

    Yes

    Windows Server 2008 Standard 32-Bit

    Yes

    Yes

    Windows Server 2008 Enterprise 32-Bit

    Yes

    Yes

    Windows Server 2008 Datacenter 32-Bit

    Yes

    Yes

    64-bit edition of Windows Server 2008 Standard

    Yes

    Yes

    64-bit edition of Windows Server 2008 Enterprise

    Yes

    Yes

    64-bit edition of Windows Server 2008 Datacenter

    Yes

    Yes

    Windows Web Server 2008

    Yes

    Yes

    Windows 7

    No

    Yes

    64-bit edition of Windows 7

    No

    Yes

    64-bit edition of Windows Server 2008 R2 Standard

    No

    Yes

    64-bit edition of Windows Server 2008 R2 Enterprise

    No

    Yes

    64-bit edition of Windows Server 2008 R2 Datacenter

    No

    Yes

    Windows Web Server 2008 R2

    No

    Yes

     

     

    The following restrictions apply to P2V operation system support:

    ·      VMM does not support P2V conversion for computers with Itanium architecture–based operating systems.

    ·      VMM does not support P2V on source computers running Windows NT Server 4.0. However, you can use the Microsoft Virtual Server 2005 Migration Toolkit (VSMT) or third-party solutions for converting computers running Windows NT Server 4.0.

    Requirements for the Destination Host Server

    In VMM, a host is a physical computer on which you can deploy one or more virtual machines. To run P2V, you need a host on which to place the image of the source computer.

    Requirements for the host server include:

    ·      The destination host during a P2V conversion can be running Windows Server 2008 with Hyper-V, Windows Server 2008 R2 with Hyper-V, or Virtual Server R2 SP1 (or later).

    ·      The destination host cannot be in a perimeter network.

    ·      As in any virtual machine creation or migration, the destination host for a P2V conversion must have sufficient memory for the virtual machine in addition to memory reserved for the host operating system. By default, the amount of memory reserved for the host operating system is 256 MB in VMM 2008 or 512 MB in VMM 2008 R2. If the host does not have enough memory for the virtual machine in addition to the memory reserved for the host, you will get a placement error in the Convert Physical Server Wizard.

     

    If you are looking for doing P2V for Linux or UNIX Servers there is a 3rd party Novel Tool Called PlateSpinMigrate it works perfectly.

     

    About the Pass Through Disks it won't happen from the First Time you have to Represent to the VM a PassThrough Disk and Copy the Contents from a partition to another and Unpresent the normal Partition, then rename the PT Disk to the same name as the old one and Give it the same letter.

     

    Yours,

    M. Abbas

    Wednesday, June 22, 2011 11:16 AM