- First, I created an image of the old server with Symantec Backup Exec System Recovery 2010; this could be done online. I just stopped all the Sharepoint, SQL, and Web Services so that no new data could be written in the time I created this Image.
- After I moved this Image to the Microsoft Hyper-V Host Server, I started to convert the v2i Image with Symantec Backup Exec System Recovery 2010 to a Microsoft VHD.
- I created a new Virtual Machine on the Hyper-V Server and added this existing VHD. (Important here: I tried to create the same Hardware environment for the VM which I had as physical Hardware before. (Dual Core with 2048MB memory) So I had no problem to start the Virtual Machine.
- Now its time to install the Hyper-v integration components (the VM Drivers) which can only be installed on Windows Server 2003 with SP2 or later. I turned off the Virtual Machine again and attached the VHD File offline on my Hyper-v Server, so I had file access to the Virtual Hard Disk. I added the Service Pack 2 file to the root of the VHD.
- After unmounting the VHD, I started my Virtual Machine again and installed the Servicepack 2 and the Hyper-v Integration components.
- Now I added more Hardware to the Virtual Machine (Quad-Core and 4GB memory). I also change the Legacy Network Adapters to standard Network Adapters (higher Network performance)
The performance of the new Hyper-v is just pretty impressive.Tags: Backup Exec, Backup Exec System Recovery, Backup Exec System Recovery 2010, HP, Hyper-V, Hyper-v r2, Micorsoft, P2V, performance, Symantec, System Recovery, Windows Server, Windows Server 2003, Windows Server 2008 R2 Last modified: July 19, 2019