Group: Forum Members
Posts: 14K,
Visits: 82K
|
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?
|