Category Archives: Vembu Hive

Writing about Vembu BDR Suite Free Edition

Vembu is a leading software product development that has been  focussing on Backup and Disaster Recovery software for data centers over a decade. It’s flagship offering- the BDR Suite of products consists of VMBackup for VMware vSphere and Hyper-V, Disk Image backups for Physical machines, Workstations. Backing up individual files and folders to physical servers and cloud can be performed with Vembu Network Backup and Online Backup respectively.

Moreover, it has multiple flexible deployment like on-site, off-site and to the cloud through single user interface. Another offering of the Vembu BDR Suite is to be able to configure item level backups like Microsoft Exchange Servers, Sharepoint, SQL, My SQL, Office 365, G Suite etc., This latest version of Vembu BDR Suite v3.8.0 has come out with the few notable features in two major offerings- one unlimited features for three virtual machines and the second thing being able to backup unlimited virtual machines with restricted features.

This latest Free edition of Vembu BDR Suite was designed understanding the setbacks by any common IT Administrator. Thence  making Vembu an important name in the market for backup vendor for its enterprise level product for SMBs. This free edition is free forever and IT administrators can continue managing their backups with the trial version without any feature restriction. Let’s take a plunge into the detailed features of this Free edition.

Unlimited features for the Limited environment(3 VMs):

 Using the Vembu BDR Suite in its trial version does not require purchasing a license. This category of the Free edition offers unlimited features and few of them are listed below:

  1. Agentless VMware backups for multiple VMs: Configuring backups for protecting multiple VMs without physically installing any agent.
  2. Disk Image Backups from BDR Server: Disk Image Backups can now be configured and managed via Vembu BDR Server. Relying on proxy agents is no longer required, unless it’s a distributed deployment which require individual proxy agent installation.
  3. Full VM Backup: Will backup the entire VM including OS, applications and the data.
  4. Storage Pooling: Storage Pools are used to aggregate the space available from different volumes and utilise them as a storage for specific backups. The hybrid volume manager of Vembu BDR Server supports scalable and extendable backup storage for different storage media such as Local drives, NAS(NFS and CIFS) and SAN(iSCSI and FC). Vembu BDR provides storage pooling option for both backup level and group level.
  5. LAN free data transfer using SAN and Hot- Add modes:Vembu VM backup support Direct SAN, Hot-Add and network transport mode to backup the VM data.
  6. Auto Authorization: Enabling Auto authorization in Vembu BDR allows proxy agents to get registered to backup server using unique registration key generated by respective BDR server.
  7. Automatic Backup Scheduling: Backups can be automatically scheduled as per the user’s flexibility
  8. Encryption Settings: Users can now provide additional security to their disk based backup jobs by assigning custom-password to backup server, such that all their backup data will be encrypted and can be restored/accessed only by providing the custom-password.
  9. FLR from GUI (Backup & Replication): File Level Recovery(FLR) is now available for both backup and replication jobs where user can choose specific files and folders from VMware/Hyper-V/Disk Image backups and VMware replication, to be restored in a quick fashion.

All the above major features are included in this free edition for 3 virtual machines.

Let’s get to know those restricted features for unlimited virtual machines.

Restricted Features for unlimited virtual machines:

All the features mentioned above for limited business environment will be applicable for these categories with few restrictions in the features. They are:

  1. Application-aware processing: Configuring them for a Hyper-V environment is restricted but that does not hold good with VMware vSphere Esxi(s).
  2. Changed Block Tracking: Only the incremental blocks which are changed since the previous backup will been tracked and  backed up in the successive backup schedule thereby reducing disk space and time
  3. Retention Policies: User can retain any number of recovery points of his own choice. They come to great use when it comes to store the backup data.
  4. Near CDP: Incremental backup can be scheduled every 15 mins to ensure the RPO < than 15 mins
  5. Quick VM recovery to ESXi: Incremental backup can be scheduled every 15 mins to ensure the RPO < than 15 mins.
  6. Automated Backup verification: Verify the recoverability of the backed up images and screenshot of the booted Image backup will be mailed

Backup and recovery holds good for both physical and virtual environments and makes granular recovery possible with great ease.You will able to scale out your storage, secure your individual backup jobs with in-built deduplication, encryption and compression that makes its own file system called, the VembuHIVE.

This latest Free edition thus becomes one of the most business-friendly and a complete backup solution. That being said,  It can be suitable for both testing and production environments! Their out-of-the box policy- backup for all was hailed even at the recent VMworld event, Las Vegas.

Well, there is nothing left to ponder now. It’s time to make the right decision. It could be done right away with getting started with their Free edition of Vembu BDR Suite on a 30 days free trial. Click here.

 

Live Recovery to Hyper-V server using Vembu BDR Suite

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

  1. 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.
  2. Live Recovery to Hyper-V server – I will cover this restore option in this post.
  3. File Level Recovery (You must install agent on the file server)

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

image_thumb21

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.

image_thumb5     image_thumb7

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.

image_thumb91

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.

image_thumb121

I could observe the restore progress details in the following screen noted below.

image_thumb15

After restoration process is completed, I went back to restore screen report to see the VM name restore along with its status.

image_thumb18

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.

image_thumb211

Before I power on the VM, I verified the network connectivity. VM was not connected to any network.

image_thumb27

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.

image_thumb24

image_thumb23

Conclusion

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.

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.  Continue reading Configure the Backup Job of a VM hosted on Hyper-v

Configuring Vembu Backup on Hyper-V

I’m starting today series of posts focusing solely on backing up VMs hosted on Hyper-V.  In these posts, I will cover the unique configurations of Hyper-V and Vembu BDR. There are striking differences in the configuration steps which I considered worth covering in these posts. Continue reading Configuring Vembu Backup on Hyper-V