Help with backup and instant restore

- Log in to post comments
In reply to Hi Russell,… by truwrikodrorow…

Thanks, I was successful in installing Acronis 12.5 advance on another workstation and running the external hard drive image via instant restore.
My question is what are the best case practices under the instant restore session? For example if the the main server is down for two or three days. Can this instant restore vm session be used like the original server was for the time period ? (boot up, serve MySQL data, store information and make normal Acronis incremental backups every hour)
I have noticed under the vm, the servers windows 10 is saying it is not activated, although it was under its physical machine ? also when the vm is shutdown, there is a 4-5 min period on the next boot up where hyperV seems to be "merging" data?
When the main physical machine has been restored they will probably be a difference in the stored data between its virtual instance and the original physical machine, what is the best way to have the virtual machine imaged so that it can be restored back to its physical form? Is this restore image made inside the instant restore vm session, or is the target machine that is running the vm host the one to make the image that allows the original server machine to be restored?
Sorry for the noob questions, but VM can be tricky to see the work flow, particularly when it is time to restore back to physical.
Russell
- Log in to post comments

Hi Russell,
Mounting a VM from backup (instant restore) on Hyper-V primary scenario is to allow services (for example web server which was running inside a failed machine) running while the full recovery is done. Note however that the changes made to VM while it's mounted from backup cannot be regularly preserved, so if the failed server is running some database, then you should consider full VM restore instead of instant one or use the method described below.
The process of persisting the data inside mounted VM, e.g. moving the data from backup onto production VM storage in background, while mounted VM is running, is called "finalization" and it's currently supported for VMs mounted on vSphere only. For VMs mounted on Hyper-V we're planning to add "finalization" support during this year and currently there is only manual finalization possible - see this thread where I described the process which might be quite tricky one.
Alternative method: To capture the changes inside mounted VM you won't be able to back it up using the Hyper-V agent, e.g. only backup via Agent for Windows/Linux installed _inside_ the guest OS of the VM will be possible. If the original (failed physical) machine was registered on the management server, then the mounted VM (from the backup of this physical machine) will also try to register on the management server since it runs Agent for Windows/Linux inside - there may be conflict. Therefore the original physical machine should be removed from the Devices list (it should appear as offline machine in this list) to avoid this and get the backups running. The mounted VM will appear twice: once as a Hyper-V VM - item 3 on attached screen shot; and once as a machine with agent inside it - item 1 on the attached screen shot (that's the type which you'll need to back up). Item 4 = regular Hyper-V VM reported by Agent for Hyper-V and item 2 = regular vSphere VM reported by Agent for VMware.
Basing on the above you can back up the mounted VM using Agent for Windows/Linux installed inside it (select item 1 type from the Devices list) and then, once you get the hardware, restore the physical machine using this backup.
The guest Windows activation indeed may be required if Windows detects hardware changes and this is something which we don't control on Acronis side or otherwise it would contradict with Microsoft licensing policy.
Thank you.
Attachment | Size |
---|---|
446722-145866.png | 27.75 KB |
- Log in to post comments