In case you loose data due to any reason you have to recover it from backup. Fortunately, you have more than one way to restore data and bring service back up into Production. In this post, we will discuss how to restore VM using one of the methods available.
In the previous post, I have performed the backup of FileServer. I’ll use FileServer to demonstrate how to restore Virtual Machine. I can restore fileserver in various ways. Although I’m describing you single VM restoration procedure, however, you can restore multiple VMs simultaneously. It is noteworthy to understand that you can restore VMs in following four ways
Instant VM Recovery –While VM is booted directly from the backup file on the Backup server, but you must remember to install Hyper-V role on the backup server. In the restore time, RTO is reduced to minute rather minutes it might take to uncompressed Backup data and restore it directly to Hyper-V server.
Live Recovery to Hyper-V server – I will cover this restore option in this post.
File Level Recovery (You must install agent on the file server)
Download – I have posted it here
Live Recovery to Hyper-V server
In live recovery option, a Full VM is restored from the Backup server to the Hyper-V. VM is automatically registered with the Hyper-V manager. To clarify here, after the restore operation is finished, VM must be connected to VirtualSwitch and powered ON manually. To put it differently, VM is restored but not attached to the network neither is turned on automatically.
Live Recovery takes more time than Instant VM Recovery, but the most compelling reason to restore by using this method is to warranty production storage performance rather than backup storage performance.
In this section, I wish to restore FileServer from the backup. I have chosen the alternate location to restore the VM and manually powered ON the VM on the Hyper-V host. Firstly, open the browser and enter the VBDR default URL https://backupserver:6061, then select the Recovery Tab, lastly choose the Backup Job name to restore the VM by clicking on the restore button. From the following four choices, I chose Live Recovery to Hyper-V server
I have to decide the restore version. The most recent backup version, In particular, i.e. 9th Dec 2300 is an incremental backup. To repeat here, Vembu only performs Incremental Forward backup which I discussed in the previous post, a process which will complete restore from full backup and apply all incremental from the time you selected till the full backup date. In the next screen i.e. screen “Choose the restore data” I have the only fileserver listed.
In Restore Options I have to provide the UNC path to download the image file. The image file format is VHDX. I have entered my admin credentials in addition to that below I have sized the RAM. Finally, before proceeding further, I reviewed the details. When I press next button, Behind the scene UNC path is verified.
At this stage, most of the necessary recovery steps are finalized. In below screen, you review the details one final time and press Yes to confirm the restoration.
I could observe the restore progress details in the following screen noted below.
After restoration process is completed, I went back to restore screen report to see the VM name restore along with its status.
I opened my Hyper-V manager to validate the restore VM name is matching with fileserve_10DEC2016_19_36_41 reported in the below screen.
Before I power on the VM, I verified the network connectivity. VM was not connected to any network.
Furthermore, I checked the VM Generation, CPU Memory, and Harddisk. VM Generation was right, but Dynamic Memory was disabled. By default, Dynamic memory settings will not be restored in the current version of Vembu BCDR suite but in the future release, it will be incorporated.
Restoring VM is as easy, simple four step procedure. VM gets restored, but you must select the network, Memory before powering on the VM. Taking into consideration, the price point Vembu is offering these features are the true reflection of value for money.