Transcript Physical To Virtual Migration

PHYISICAL TO
VIRTUAL
MIGRATION (P2V)
John Kelbley
Senior Technical Product Manager
[email protected]
860-678-3107
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
Introduction
John Kelbley
[email protected]
 Senior Technical Product Manager
with Microsoft’s Platform Tech
Strategy Team
(Redmond-based group)
 Field-based “corporate” resource focused on
customer and partner engagement for new
server technology
 Server Virtualization
 High Performance Computing (HPC)
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
Types of Migrations
 P2V = Physical to Virtual- Conversion of a
physical host to a virtual instance
 V2V = Virtual to Virtual – Migration from
one virtualization platform (or host) to
another
 V2P = Virtual to Physical – Conversion from
a virtual instance to running “on the metal”
Phyisical to Virtual Drivers
 Target hosts often include older systems
saddled with:
 Hardware maintenance costs
 Spare-part availability challenges
 Vintage operating systems & applications
 Unsuppored by vendor
 Vendor out of business (no where to be found!)
 Limited or no backup “awareness”
 Limited or no failover capability (HA)
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
P2V: Risk Versus Reward
 Virtualizing older, unsupported systems
doesn’t extend support from sofware vendors
 P2V can drastically reduce risk of failure
 Regardless of support status, eliminating
high-risk hardware can be a good thing
 Virtualizing means new opportunies for:
 Backup and recovery
 High Availability
 Management and monitoring
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
High-level Migration Steps
1. Assess the existing configuration
2. Capture the configuration
3. Capture disk image(s)
4. Transpose disk image(s)
5. Disable the legacy system
6. Transpose the configuration
Configuration Assessment
 How much RAM is required for the VM?
 What are the disk requirements and





anticipated growth?
How many network connections are
required?
Do the MAC addresses need to be
preserved?
Does the system require significant CPU?
How many cores can the system use
require?
Hardware specific software to be removed?
Data Collection: Local
 Use command line tools on physical
host to “persist” configuration info
locally
IPCONFIG /ALL >c:\IPCONFIG.TXT
 WMIC works on XP / 2003 and newwer
Wmic
Wmic
Wmic
Wmic
Wmic
os > c:\os.txt
qfe > c:\patches.txt
baseboard > c:\baseboard.txt
cpu > c:\cpu.txt
nic > c:\nic.txt
Data Collection: MAP Toolkit
 Microsoft Assessment and Planning (MAP)
toolkit is a free download that can inventory,
assess, and report on your environment
http://www.microsoft.com/virtualization/downloads.mspx
 Collects performance data over time including
historical measurements for
 Processor
 Network
 Disk
 Can inventory harddware & software all at once
 Creates Excel formatted reports you can use
Configuration / Disk Capture
 Configuration data should have
already been captured – requires
review
 Any cricual “parts” that will not
virutalize (USB, voice, A to D)?
Configuration / Disk Capture
 Dedicated P2V Tools
 Acronis, PlateSpin, Vizioncore, VSMT, and (my favorite) SCVMM
 Backup and Recovery Tools
 Often havea bootable “recovery disk”
 I use Windows Home Server!
(completely unsuported!)
 Disk imaging works well
 Ghost (cost money)
 ImageX (donesn’t cost money)
 Part of Windows Vista / 2008
 WAIK
Windows Automated
Installation Kit (WAIK)
 Ddesigned to help customize and deploy
Windows operation systems
 Can help perform
 Unattended Windows installs
 Capture / deploy Windows images with ImageX
 Create Windows PE images
 You can download the WAIK from Microsoft
in the form of an ISO image file
Disk Capture /
Dissable Phyisical Host
 Boot Physical host with WinPE
 Capture disk image(s) with ImageX

Imagex /Capture c:\ d:\my_server.wim “My Server”
/verify
 Turn off / disconnect physical host
Transposing Configuration
 Construct VM comfiguration to mimic
physical host requirements
 RAM, Logical Processors, NICs, Disks
 Add “Legacy Adapter” if network support
requred for image deployment
(drivers should be in WinPE already)
Dissabling Phyisical Host
 Boot Physical host with WinPE
 Capture disk image(s) with ImageX

Imagex /Capture c:\ d:\my_server.wim “My Server”
/verify
Transposing Disk – Prep Disk
 Easisest to “install” actual OS to prep
disk (VHD) properly, or try to prep
manually (bad idea)
 Boot from WinPE ISO (or CD)
 Diskpart
 Select Disk 1 (could be different)
 Create Part primary
 Assign (get a drive letter)
 Format fs-NTFS quick
 Exit
Transposing Disk
 Apply image(s) with ImageX
 ImageX /apply d:\2k3.wim 1 c:
/verify
Transposing Disk-NEWSFLASH!
 WIM2VHD Available to public!
 Converts Windows Imaging Format
to VHDs!
http://code.msdn.microsoft.com/wim2vhd
Transposing Configuration
 Modern versions of Windows do a good job of
detecting new hardware components
 Changes to the number of processors (cores) / type
 Repair option from startup media can correct many startup
anomalies
 Issues to manaully correct might include:




Add Integration Components (ICs)
Advanced Configuration and Power Interface (ACPI)
Uni / multiprocessor capabilities
For Windows 2000, you may need to reinstall the operating
system over the existing installation (as per KB246236) or
take other actions (as described in KB249694)
 Automated migration tools can detect and address many
troublesome migration issues
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
ImageX Deployment with WinPE
Manual P2V Limitations
Using SCVMM
Using SCVMM
Using SCVMM
Using SCVMM
Summary
 Phyisical to Virtual (P2V) migrations
may be necessary in some situations
 Manual P2V tools are available for free!
– you get what you pay for
 System Center Virtual Machine Manager
(SCVMM) includes excellent P2V / V2V
support
Agenda
 Introductions
 Migration Drivers and Challenges
 Migration considerations
 Migration Process
 Walking through a physical-to-virtual
(P2V) migration
 Q&A
Q&A
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to
changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the
date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Virtualization Resources

Microsoft Virtualization



Web: http://www.microsoft.com/virtualization
Technet: http://technet.microsoft.com/enus/virtualization/default.aspx
System Center Virtual Machine Manager

Web: http://www.microsoft.com/scvmm

Hyper-V

http://www.microsoft.com/windowsserver2008/en/us/hyperv.aspx
Microsoft Application Virtualization (formerly SoftGrid)
 Web: http://www.microsoft.com/systemcenter/appv/default.mspx

Terminal Services




Blog: http://blogs.msdn.com/ts/
Web: www.microsoft.com/terminalserver
Virtual PC 2007

Web: http://www.microsoft.com/virtualpc
Virtualization Road Map
Now
Windows Server 2008
Microsoft Server 2008
Hyper-V
System Center Virtual
Machine Manager 2008
MDOP w/ MAV4.5
Updated w/ Server 2008
guest support