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)
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.
I believe the best method to learn any technology is to teach someone or implement it. I prefer to deploy and try out for myself. Having said that I’m open to teaching if required. I have recently started exploring the feasibility of using Windows Server 2016 Nano for the Production environment. There are at least four use cases for Windows Nano one of them is using Windows IIS Server which I will describe here. Given that I know I have IIS role available on Nano I was examining to put this in right learning form. The closest and easiest I could think of Web Server is required for vSphere Update Manager (VUM) when it is configured in Air-Gapped mode.
So let’s get rolling so that we can take a look at it.
Here is the list of things we need to Build an Air Gapped VUM
Web Server in DMZ
Operating System for Web Server
Storage space for Update Repository
Optional but Strongly recommended to have Certificate Authority configured.
Installing Nano Server with IIS Package
Nano server can be deployed using two methods. The First method which is very popular is PowerShell and second method know to few is the GUI based. I’ll cover here PowerShell approach while GUI based approach is covered here
So what we need to achieve our goal. [Pre-requisites]
I will cover it in two part. In part01 I will cover how to Package, Install and Configure Nano server. In part02 I will cover how to set up IIS server.
As a first step, you must import Nano Server PowerShell package. Where is this package? Well, it is in Windows 2016 ISO. Double click ISO. It will automatically mount. Open Powershell ISE (Elevated Prompt) and run following command to import NanoServerImageGenerator Module
To confirm whether the NanoServerImageGenerator Module is imported, type the following command. Yes ! Only three commands and 99% of the time you will use only one command.
Now before you start the process of creating the image, you might need to find the package name. To find package name, you must install package provider.
Now before start the process of creating image you might need to find the package name. To find package name you must import package provider. Install-PackageProvider -name nanoserverpackage
If the above installation is successful, then you should be able to find the following command
and the output of the command will be exactly as below
Create Nano Server Image
Once our pre-requisites are ready, then we can start building Nano Image. As mentioned above, you need either Windows 10 or Windows Server 2016 to create this image and working directory. I have used Windows Server 2016.
Now let’s begin the process of creating Nano Image. I’ll be building Virtual Image. Assuming you are still in Powershell session, type the following command. Below screen capture is from Powershell and not from PowerShell ISE. I’m not aware how to create multiple lines of codes in Powershell ISE. After pressing Enter on the preceding command, you will be prompted for the Administrator password. Supply the password to begin image building process.
I have tabulated the parameter of the command below and provided explanation against each.
Standard or Enterprise a decision If you will use Hyper-V
Guest or Host. Guest is for Virtual Machine and Host is for Hyper-V. If you are going to host Hyper-V role on it, then the role is Host
The package you wish to deploy. To find out the package available, please refer to screen capture with Title ‘Find-NanoServerPackage’ above. In my case, I have to select IIS Package
You will typically deploy Server with Static IP. For IP Address, Subnet Mark, Gateway and DNS Server
Enable Remote Management. This port is a must.
Name of the server. This name is the Guest OS name
Path to ISO. It is the path of ISO image
Path where to create Image i.e. VHDX file which will be our working directory
Name of the Network Card. In all cases it is Ethernet.
There are other parameters which I have not used here as it is not required.
Now our image is ready to be deployed, So let’s deploy it. Before you do that copy .vhdx file into Hyper-V working directory.
I’m using Hyper-V manager. Detailed eight steps procedure is captured in the screen capture below.
A point to note is in Step:04 you must select Generation:02 as we have selected VHDX extension while creating NanoServer Image.
After you press Finish, Nano VM is created, and it is ready to be powered on. Why not power it on then? Power on the Virtual Machine. VM will be powered on immediately, but it will take few seconds to join to the domain and Install IIS Package. After that few seconds gap, you will be looking at the console of brand new Nano Server
There is no practical need to login to this console as we have already configured IP Address, DNS and domain join. In the below screen I have logged in using contoso.com credentials. This screen is referred as Nano Server Recovery Console. The recovery console screen is to reset Networking configuration.
As we are here, let’s take a look at our available options.
I always like to enable Ping on all Windows Server leaving firewall enabled. Click on Inbound firewall rules, press Enter scroll down till you see ICMP IPv4 shown below. Press enter to modify the rule by press F4 which will toggle Enable or Disable. It is the only rule you can change in this console. You might think, hey! Wait I can achieve similar thing from GroupPolicy. But GroupPolicy is not supported on Nano
Though I have shown how to achieve it here, it is not the requirement.
Manage Nano Server using Server Manager
Open Server Manager from our working server and follow the steps mentioned or the screen capture for the steps
Click on All Servers
Right click and Add Server
Select Find Now and choose the NanoIIS03 from the list
Move the compute
If Firewall ports are opened, the Online status will be immediately visible.
Before We conclude this post, let me walk you through the basic configuration you might have to do on the nano server.
Set Time Zone on Nano Server
Time Zone must be changed to match to your region. It is critical to check if the time of the server is matching. If the time difference is more than 5 minutes Domain, Join will fail.
Remote into nano Server using our familiar command
Enter-PSSession -ComputerName $VMName
Set-TimeZone-Name"Arabian Standard Time"
Increase the Disk Size on Nano Server
Right click on Nano server, then select settings
Find the Hard Drive and press Edit as shown below
Provide the new size. Note I have skipped few unimportant screens. In below example, I have increased the size from 4 GB to 10 GB
Enter New Size to Expand DiskPress finish which will increase the disk size. This action will increase the disk size but not at the disk level. To the extent the C:\ you need to get disk and partition details in a variable and then use max size method to increase it.
Get Partition command will give details of Partition available on Nano Server. I’m assuming you still have the remote session on nano server.
Select the right partition. In my case, it is Disk 0 and Partition 4. Capture output of this command in variable $Extvol.
Configure the Backup Job of a VM hosted on Hyper-v
Like all backup product, Vembu also needs job to carry out backup of VM. We will together follow the backup job wizard. First step is choose VM or VMs. One backup job could be used to process more than one VMs. In Choose Virtual Machines screen which primarily lists down the inventory of VM managed by Hyper-V we select single VM. To start, I selected the vdc2017 which is Domain Controller in my case. It is noteworthy to point out how smartly the VM status is displayed in the screen below. Continue reading Configure the Backup Job of a VM hosted on Hyper-v→
We can use Vembu to migrate VMs to any hypervisor. Such tools are available in the market, but what is unique about Vembu it offers this feature as a part of the backup suite. I can backup VM in VMDK (VMWare) format and restore it to hyper-v format. This Feature can of great use if you are using different hypervisor in DR than in production. Let me describe the use case.