Macrium Support Forum

Restoring modified viBoot image to original physical system

https://forum.macrium.com/Topic35821.aspx

By jphughan - 17 April 2020 7:43 PM

I've noticed that before the initial boot of a given Reflect image, viBoot seems to go through a sort of ReDeploy process, which makes sense given that a Hyper-V VM would certainly be "dissimilar hardware" relative to the original physical system from which the image was captured.  But if I were to use the Backup function within viBoot to capture a new Reflect image backup of the VM's current state and restore THAT back onto the original physical system, would I have to ReDeploy the restored image on that physical system to set it up for booting from that physical hardware again?  Or does viBoot have some way to create a new backup that contains the changes I made within the VM without also including the ReDeploy changes that allowed the original backup to boot within Hyper-V in the first place?
By JamieW - 20 April 2020 7:41 AM

jphughan - 17 April 2020 7:43 PM
I've noticed that before the initial boot of a given Reflect image, viBoot seems to go through a sort of ReDeploy process, which makes sense given that a Hyper-V VM would certainly be "dissimilar hardware" relative to the original physical system from which the image was captured.  But if I were to use the Backup function within viBoot to capture a new Reflect image backup of the VM's current state and restore THAT back onto the original physical system, would I have to ReDeploy the restored image on that physical system to set it up for booting from that physical hardware again?  Or does viBoot have some way to create a new backup that contains the changes I made within the VM without also including the ReDeploy changes that allowed the original backup to boot within Hyper-V in the first place?

HI @jphughan,

The “redeploy” functionality in viBoot simply adds the relevant drivers to the OS installation to allow it to boot inside a Hyper-V virtual machine.

This should not prevent any backup of the VM from booting on physical hardware, however; this may not hold true if operations inside the running VM (e.g. Windows Update, registry cleaners, etc), modify the system configuration in a way which undermines this.
By jphughan - 20 April 2020 1:19 PM

Sounds good, thanks Jamie! Smile