Configure the Backup Job of a VM hosted on Hyper-v

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. 


VMs/Disks Exclusion is critically important from two angles. First of all it is useful in backing up only data which is required rather backing up all the VM Arguably increasing the data size. Second it is gives you opportunity to restore VM without going through complete deployment of OS/Installing Application.

After this step, press Next to select the frequency of backup. I have selected it to Run Daily 04 AM in the morning.



Another step is to configure retention policies for the backup job. I willingly kept retention policy for the backup job as default. Default is to keep last 3 copies. In this example I left Application Aware, Additional Full Backup options as default. In Vembu BDR, all backup jobs by default are configured to perform full backup and there on only incremental backup which is referred as forever incremental backup job. In any case, full backup of the VM can configured using “Edit Additional full backup” shown below.


Finally, in the Review Configurations Wizard Step, I gave the name to the backup job.  To test the backup job, I selected the to Run this backup immediately which will fire the backup job right away.


Another Interesting things I came across is status of backup is seen in Hyper-V manager console.  Monitoring is paramount importance to ensure services are offered uninterruptedly to the end user.


Below backup is progressing at much better rate than I was expecting in lab. I see approximately 270 Mbps is seen. 8 GB of backup was completed in 4 minutes. After a backup job is finished, backed up data is stored in the backup repository which I have configured previously illustrated in this post.

image451_thumb2   image37_thumb2

Incremental backup of same VM is finishing in less than a minute. First is Full backup of 9.31 GB, second is just 5% of full backup and subsequent backup size is decreasing at exponential level, Consequently backup windows is drastically decreasing, as a result less disruption to the VMs being backed up. What is the magic behind this? Well it is Change Block Tracking (CBT). CBT keeps the list of data blocks, before performing backup it uses this list to compare it with block of data to be copied. If block has not change it is not backed up. As a matter of fact, below VM has not changed since it was full backup which explains the reason why CBT is at it is highest usage.


In Vembu BDR suite, you can configure only incremental forever backup. As a result incremental backup backup set are saved next to full backup set which you can be noted below. It is equally important to recall the Vembu’s propriety file system (Vembu Hive) where  Meta data, Backup files (in 100 MB chunks) are stored in different folders. To check these files open Windows Explorer browse to Backup repository (S:\ in my case) expand the folder Repo_3. It is important to point out that there are multiple Repo folders and each repo folder represents VM backup data


Over all I see Vembu has packed a lot of features in their backup product. While I created a separate blog post of configuring Vembu and Hyper-V,  yet there are lot of similarities between vSphere and Hyper-V on Vembu.