Is it possible the following scenario - Physical server 2008 VHD backup file, created by wbadmin.exe to run in Hyper-V server?
One of our physical web servers is running Windows Server 2008 Standard x64, and is being backuped daily by default backup utility for server 2008 (wbadmin.exe).
I am curiuous is it possible to restore this VHD backup file into Hyper-V server (said in other way to create new VM using that VHD image).
If it's possible - what are the steps to successfully do this?
I am curiuous is it possible to restore this VHD backup file into Hyper-V server (said in other way to create new VM using that VHD image).
If it's possible - what are the steps to successfully do this?
Nope, won't work.
But, this will:
- Prepare a fresh VM with the same OS.
- Shut down the VM and mount the VHD file on another VM
- Mount the "backup" VHD you'd like to restore from the same VM
- Use robocopy /purge /b /e /copyall to take all the data from the backup vhd to the new VHD
- Shut down the VM and mount the VHD file on another VM
- Mount the "backup" VHD you'd like to restore from the same VM
- Use robocopy /purge /b /e /copyall to take all the data from the backup vhd to the new VHD
After this, shut down the VM, and you should be able to create a new VM using the destination VHD file. It will boot - all you have to do is install integration services.
Now for some more "magic":
You can use vshadow.exe to create a VSS snapshot of a running physical OR virtual machine and expose it to a drive letter (yes, boot drive also), and use the robocopy trick above to perform P2Vs or V2Vs. What's good about this method is that you can do a first pass with the machine still servicing requests, then stop all critical services and do another pass to complete the process. Typically takes about 2-3 minutes, depending on how much data has changed. Robocopy will only copy files which are different, and also copies NTFS permissions.
Note:
1) You may need to use DriverInjection (http://www.911cd.net/forums//index.php?showtopic=22523&st=0) or something similar if the standard IDE driver is not present on the source.
2) You may have to edit boot.ini to point to partition 1 - some system manufacturers have a utility partition as #1.
2) You may have to edit boot.ini to point to partition 1 - some system manufacturers have a utility partition as #1.
Otherwise you should be good to go.
References:
How to configure WSB with the support for Hyper-V VSS writer.
No comments:
Post a Comment