16,755 pts.
 Performing a Virtual Server to Physical Server Migration
Because of limited hardware resources, I am using VMware Server 1.5 in a lab environment to build and test a Windows Server 2003 DOMAIN consisting of 8 servers on one physical host. Once this virtual DOMAIN is functional and successfully tested, I will need to move it to a production LAN consisting of 8 physical machines. I was not successful in performing a V2P migration using the method documented in VMware’s Virtual to Physical Migration Technical Note. Can anyone recommend an alternate tool or method for performing a V2P migration? When I originally built the Virtual Servers I made sure to configure the appropriate hardware options to match the target physical systems (i.e. 1 processor, SCSI Controller, etc.). Once the image of the VM created using Symantec Backup Exec System Recovery v.6.5 is restored to the physical target, I have no issues with driver recognition, but I am unable to boot past the W2K3 Recovery Console. The boot.ini file looks good. I am new to virtualization and am attempting a simple application of the technology so any insight would be greatly appreciated.

Software/Hardware used:
ASKED: October 7, 2008  7:00 PM
UPDATED: January 21, 2009  7:26 PM

Answer Wiki:
Platespin's <a href="http://platespin.com/products/powerconvert/uses.aspx">PowerConvert </a>can do V2P conversions, it's not a free product though. You might also check out <a href="http://www.rtfm-ed.co.uk/?p=210">DDChanger</a> which is free. ------------ V2P is a problematic subject as it relies on the HAL to be correct for the driver to allow boot, once this boot takes place past the ntKernel a driver relaod will take place. you will find only specific subsets of chips and hardware will be supported for V2P due to these contrains, the first real question would be what hardware are you using? HP have a plugin which enabels V2P on proliant hardware so check the manufacturer first to see if a V2P method is avaiable for the Vendor, then check platespin and check it compatibitly list. then have a look in the forums to se what other people are using as per link above for help and advice, (oh your here! :) ) Hope this helps in some way PS --------------- For those of you interested in Virtual to Physical Migrations (V2P) ... My 2 cents ... I tested the following V2P Migration Methods/Tools: - V2P Migration Method documented in the VMware Technical Note: Virtual Machine to Physical Machine Migration - PlateSpin PowerConvert v7.0.0 Workload Portability Tool - HelperApps DDChanger v1.2 - Symantec Backup Exec System Recovery (BESR) v6.5 with Restore Anywhere - Acronis True Image Echo Server for Windows with Universal Restore Add-on Here is a summary of the outcome of my testing: Virtual to Physical System Migration was best achieved with both the PlateSpin PowerConvert and Acronis True Image Echo Server with Universal Restore applications. Preliminary and post migration manual configuration requirements were minimal as compared with the other V2P methods. Both products provide intuitive user interfaces and detailed logging of the migration process. The PowerConvert application offers detailed source and target system analysis and reporting. The primary difference between the two V2P methods is that the Acronis product migration concept is based on the restoration of a system image whereby the PlateSpin product migration concept is based on copying/moving a system workload to a target through a management station.
Last Wiki Answer Submitted:  January 21, 2009  7:26 pm  by  Blithespirit   700 pts.
All Answer Wiki Contributors:  Blithespirit   700 pts. , Eric Siebert   675 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _