Vembu BDR Suite v4.0 GA- Release Notes

Vembu BDR Suite 4.0 is now out for production setups with many new features, functionalities and performance enhancements.

Gain quick insight into the new release and learn what you can avail from it. Get started with protecting your virtual and physical IT environment with the new Vembu BDR Suite v4.0. You can perform a fresh installation or upgrade from the older version of Vembu BDR Suite to the latest v4.0

Note: We have updated the proprietary drivers of Hyper-V & Disk Image backup in Vembu BDR Suite v4.0. If you are upgrading from older versions of Vembu BDR Suite to Vembu BDR Suite v4.0, a new backup job with the same name and same configuration will be created for the Hyper-V and Windows disk image backups and an additional full backup will be scheduled. However, the older backup data is made available on the recovery page for restore purposes on both BDR & OffsiteDR servers.

Refer the KB article: 4.0 Changelog – Vembu BDR Suite Migration for more details.

What’s new in Vembu BDR Suite v4.0?
New Features

Hyper-V Failover Cluster Support

Support for backup and recovery of VMs running on Hyper-V Cluster setups. The scheduled backups will not be interrupted even when the VMs move from one node to another for High Availability.

Checksum Based Incremental Tracking

The modifications made on the VMs running on Hyper-V servers are by default tracked using CBT technology. When CBT fails, the checksum-based incremental tracking is leveraged ensuring seamless backups.

Shared VHDX Support

Support for backing up shared VHDX of Hyper-V

New Credentials Manager

Credentials of the VM hosts, guest VMs and physical computers can now be managed using the Credentials Manager, avoiding the need to enter the credentials every time.

New Enhancements

Handling new disk addition

Any newly added disk to a VM on VMware/Hyper-V was backed up only on the next full backup. From v4.0, the new disk additions are designed to be detected and considered for back up on the next incremental schedule.

Reconnection for VMware & Hyper-V backups

If a VMware or Hyper-V VM backup job gets interrupted due to network failure, reconnection attempts will be made to continue the data transfer.

Abort Replication in Vembu OffsiteDR Server

Abort active replication jobs from within the Vembu OffsiteDR server console to terminate an ongoing replication from Vembu onsite to offsite server.

Activate/Deactivate from Vembu OffsiteDR Server

You can activate or deactivate Vembu BDR Servers from Vembu OffsiteDR if you wish to stop the backup replication to the DR site.

Live Recovery to VMware and Hyper-V

Live Recovery to VMware and Hyper-V servers is now enhanced where you can configure the virtual hardware specification of the target host like socket and core counts, memory, hard disk provision type, and network adapter while performing the permanent recovery.

Enhanced Application-aware processing for Hyper-V & VMware VMs

By default, application-aware processing is enabled for highly transactional applications like Exchange, SQL, Active Directory and SharePoint running inside VMs on Hyper-V server. v4.0 provides log truncation and application-aware processing with inbuilt parity check, and you have the option to select VMs that need them.

Quick VM recovery Report

This report will give you an insight into Quick VM recovery job details like the RTO, start time & end time, the name of the VM that was triggered for recovery, the target server etc., covering the job’s status.

Storage Utilization Report

With the new set of APIs, generate report on storage utilization with details like the size of VM before the backup schedule, the actual size of the backup data in the storage repository, compression , storage reduction rate, etc.

Major features in Vembu BDR Suite

Agentless VMware Backup & Replication

Vembu has designed VMware backup to protect vSphere and vCenter environments using VMware vStorage APIs (VADP). You can backup and replicate unlimited VMs from VMware vSphere ESXi hosts without installing an agent inside the VMs. Direct Hot-Add and SAN transport mode provide faster data transfer speed with less resource utilization. VMBackup will auto analyze the VMware environment and assign the appropriate data transfer mode.

Agentless Microsoft Hyper-V Backup with CBT Incrementals

Backup VMs running on a Hyper-V host without installing an agent on individual VMs. Vembu’s proprietary Changed Block Tracking driver tracks the changed blocks in an efficient manner and runs quick incremental backups.

Disk Image Backup for Windows Servers and Workstations

Configure image backups of Physical Windows Servers and Workstations which includes the operating system, applications, and user data for entire machine recovery or disaster recovery or to instantly access the machine in any virtual environment via quick boot options.

Native Tape Storage Support

In addition to Vembu OffsiteDR and Vembu CloudDR as Offsite copy management, Vembu BDR suite extends its support for native tape storage as well. Users can now archive a copy of their backup data to tape medias or libraries.

File & Application Backup for Windows, Linux & Mac

Vembu supports file and application level backup for all Windows, Linux and Mac operating system running machines. Backup support to system folders such as My Documents, My Photos, Desktop, Browsers and etc., are also available.

Advance Reverse Incremental with Any-Point-In-Time-Full

Since every incremental is a self-sufficient snapshot with pointers to the blocks in VembuHive File System, any incremental is instantaneously available as a full backup. There is no extra processing to restore an incremental backup compared to a full backup (no need for a merge).

Bare Metal Recovery

The entire crashed physical system can be restored to the same or new hardware by using Vembu Recovery CD.

Automatic Backup Verification

Vembu BDR Suite image verification process ensures that disk image backup data (physical disk image, VMware and Hyper-V) is in a bootable state. The integrity of backup data can be easily verified by monitoring the screenshots of the boot screen everyday.

Quick VM Recovery

This provides the flexibility to boot any incremental VM and physical machine disk image backup instantly. For Windows based Vembu BDR backup servers, machines are recovered instantly with Microsoft Hyper-V and VMware ESXi. In the case of Linux based Vembu BDR backup servers, Quick VM recovery is done with the help of KVM and VMware ESXi.

Permanent VM Recovery

The backed up VMware and Hyper-V VMs can be permanently recovered to the same or different hosts after any major disaster or VM crash.

Basic & Advanced Retentions Policies

The Multilevel GFS retention reduces the time taken to restore backed up machines and most importantly reduces the size of image files in storage location. It also avoids retaining long chains of incrementals and helps meet the requirements of your retention policy.

Cross Platform Migration for VMware, Hyper-V & Physical Windows Disk Image Backups

Since VMware, Hyper-V and Physical Windows Disk Image backups are stored at block level in a neutral format, Vembu BDR Suite makes it possible to instantly restore any incremental backup in any virtual disk format including VHD, VHDX, VMDK, VMDK-FLAT or IMG

Failover and Failback

You can instantly failover the replicated VMware VMs from the source hosts on the target host during a VM crash. You can also failback the control to source ESXi host at anytime.

Vembu Universal Explorer

Vembu developed an exclusive free tool called Vembu Universal Explorer to instantly recover the individual Microsoft application items from the backed up data. Be it physical or virtual machine data, Vembu Universal Explorer recovers application items from Microsoft Exchange, SharePoint, SQL and Active Directory without restoring the entire VM backup and disk image backup.

Free Edition Support

Vembu introduced Free Edition in v3.7.0 release. From then, users can backup VMware, Hyper-V and Physical Windows Server with limited features at free of cost after trial period.

System Requirements

Vembu BDR Backup Server

Supported Windows OS Windows Server 2016 (Essentials, Standard, Datacenter),
Windows Server 2016 Core (Standard),
Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter),
Windows Server 2012 R2 Core (Standard),
Windows Server 2012 R2 Hyper-V Server,
Windows Server 2012 (Foundation, Essentials, Standard, Datacenter),
Windows Server 2012 Core (Standard),
Windows MultiPoint Server 2012,
Windows Server 2008 R2 (Standard, Enterprise, Datacenter),
Windows Server 2008 R2 Core (Standard),
Windows 10 (Pro, Enterprise, Enterprise LTSB)
Supported Linux OS Ubuntu 16.04,
Ubuntu 14.04,
Ubuntu 12.04
Architecture 64 bit only
Memory Minimum: 8GB
Recommended: 16GB
CPU Minimum: Quad Core Xenon Processor
Recommended: Octa Core Dual Processor
Meta Data Storage 10% of the planned total backup data size.
Network Card 1 Gbps & above
Browser IE v11, Firefox v28 & above and Chrome v34 & above

Vembu OffsiteDR Server

Supported Windows OS Windows Server 2016 (Essentials, Standard, Datacenter),
Windows Server 2016 Core (Standard),
Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter),
Windows Server 2012 R2 Core (Standard),
Windows Server 2012 R2 Hyper-V Server,
Windows Server 2012 (Foundation, Essentials, Standard, Datacenter),
Windows Server 2012 Core (Standard),
Windows MultiPoint Server 2012 ,
Windows Server 2008 R2 (Standard, Enterprise, Datacenter),
Windows Server 2008 R2 Core (Standard),
Windows 10 (Pro, Enterprise, Enterprise LTSB)
Supported Linux OS Ubuntu 16.04,
Ubuntu 14.04,
Ubuntu 12.04
Architecture 64 bit only
Memory Minimum: 8 GB
Recommended: 16 GB
CPU Minimum: Quad Core Xenon Processor
Recommended: Octa Core Dual Processor
Meta Data Storage 10% of the planned total backup data size.
Network Card 1 Gbps & above
Browser IE v11, Firefox v28 & above and Chrome v34 & above
Note: For more details on the system requirements and the supported platforms, please refer this link:
Installer Downloads

Download Vembu BDR Backup Server installer from the following URL:

Technical Documentation

Refer following URL to refer Vembu BDR Suite technical documents,

Known Issues & Limitations

VMware Backup:

  1. VMware backup does not support backup of virtual machines with independent disks
  2. Application-aware backup is not supported for 32 bit Guest OS
  3. Vembu VMBackup does not support backing up of the VMs on the free edition of ESXi as the VMware vStorage APIs are not extended to the free editions
  4. VMware backup is not supported if the virtual disk resides in RDM datastore
  5. VMware backup is not supported if the Guest OSes are in hardware version 7
  6. In VMware backups, if any snapshot is reverted, further incremental backups will fail
  7. To use VMware Hot-Add Data transfer mode, the agent must be installed on the virtual machine on the same ESXi server where the source VMs reside
  8. If the proxy VM in which the backup agent is running is on a VMFS 3 datastore, the volume on the proxy VM should be formatted with appropriate block size given below, depending on the maximum disk size of the source VM(s)
    • 1MB block size – Support up to 256GB
    • 4MB block size – Support up to 1024GB
    • 8MB block size – Support up to 2048GB
  9. The disks that are to be Hot-Added must be SCSI. IDE drives are not compatible with HotAdd
  10. The proxy VM should be installed with VMware tools and the tools should be upgraded immediately to the newest available version
  11. Linux VMs are not supported for Network Mapping & Re-IP Mapping
  12. VMs with GPT disks are not supported for Network Mapping & Re-IP Mapping
  13. Application-aware backup requires administrator privileges of OS drive agent installation
  14. Backup/Replication of Encrypted VMs in vSphere host v6.5 is not supported
  15. Backup/Replication of VM name with special characters { } will fail with modular exception error
  16. Backup/Replication of VMs may fail with “VMware Modular exception error” if there is compatibility/permission issue with the ESXi and the respective vCenter
  17. Backup/Replication of VMs with special character {} in configuration files or file/folder path will fail
  18. If SSL is not enabled for a particular host, backup and restore is not possible
  19. Replication will fail if the target ESXi host’s datastore is renamed in between schedules
  20. If the replicated VM is deleted from target host, further schedules will fail
  21. If target VM name is given with special characters for live restore, unsupported characters will be removed from target VM
  22. In Disk level recovery, if the target VM does not support SATA controller, SATA disks will be restored as SCSI disk
  23. Quick VM Recovery to Hyper-V Manager of VM whose boot disk is SATA is not supported
  24. Dynamic disks can only be recovered through Live recovery to ESXi
  25. Image integrity check for VMs with GPT as boot disk is not supported for Guest OS less than Windows 2012
  26. VM with special characters in name * ? : | cannot be downloaded in virtual file formats
  27. New disk attached will not be reflected while performing Quick VM Recovery to ESXi for that schedule

VMware VM Replication with Failover and Failback:

  1. CD/DVD drives of virtual machines will not be replicated to the target host
  2. Resizing virtual disks after initial replication in the primary site will result in replication job failure permanently. A new job needs to be configured to perform the replication
  3. If the ethernet adapter configuration of the source VMs is VMXNET3, then the adapter configuration will not be replicated to the replica VM
  4. If the initial replication job fails intermittently during replication, users have to delete the replica VM in the target site and create a new job to perform the replication
  5. The VM should not be manually powered off or powered on after the Failover & Failback respectively. This may lead to data loss
  6. If the VM Failback fails intermittently, the Failback VM has to be deleted from the target site and the process has to be tried again
  7. Initiating a Failback only for the modified data after failover is not supported
  8. Once after Permanent Failover & Commit Failback, the replicated VM will be excluded from the replication job. The same should be configured again for replication
  9. Re-IP Mapping is not supported for Windows 7(32 bit) Professional Machine
  10. IPv6 configuration is not supported for Re-IP Mapping
  11. Re-IP Mapping option is not supported for VM Replication in Linux based Backup Servers

Hyper-V Backup:

  1. PowerShell should be installed in Hyper-V host machines to configure Hyper-V backup
  2. Guest VMs running on operating systems which do not support VSS such as Microsoft Windows 2000, Windows NT 4.0, Windows XP and all Linux OSes will remain in a saved state while the VSS snapshot is created
  3. Virtual machines without Hyper-V Integration Services installed will remain in a saved state while the VSS snapshot is created
  4. VMs running on Windows Server 2008 are not supported for backup
  5. VMs running on Windows 2008 R2 CSV environment are not supported for backup
  6. VMs with checkpoints (*.AVHD & *.AVHDx) will not be backed up. To perform a backup, checkpoints need to be removed
  7. For application consistent backup, the guest machines should be installed with the latest Hyper-V integration services
  8. Flat VMDK restore is not supported for generation 2 guest OSes with more than 2TB disk
  9. Live restore to Windows Server 2008 R2 and Windows Server 2012 is not supported for Generation 2 guest machines
  10. Datastore created by Vembu BDR/Vembu OffsiteDR server during Quick VM Recovery will not be auto-removed when unmounted in Vembu console
  11. 6 GB RAM will be assigned by default for VMs booted during Quick VM Recovery in VMWare ESXi
  12. Backups for Shared VHDX in Hyper-V 2016 is not supported
  13. During Quick VM Recovery and Live VM Recovery the Shared VHDX cannot be used as a normal disk
  14. When VMs are migrated to a new node and Vembu Integration Service is not installed in that node, then backups will fail
  15. Email Report will not be not sent for Live Restore to Hyper-V in successful completion
  16. Performing Quick VM Recovery on Hyper-V of Windows Server 2008 R2 & 2012 will attach & boot only the OS disk
  17. During a Live Recovery, VM creation will fail if the VM name or the target location has apostrophe(‘) in it
  18. Backup of VMs with Scale Out File Server in Hyper-V cluster will fail
  19. Hyper-V Cluster VM backup with its disks in Storage Space Direct is not supported
  20. In Hyper-V Failover cluster setup, Vembu Integration Service needs to be pushed manually for the newly added node
  21. Recovery of Generation 2 Linux OS with UEFI partition (secure boot enabled) will not work as no “.efi file” is found during restore
  22. Backups will hang for the VMs on Windows 2008 R2 Hyper-V Host with Execution policy ‘AllSigned’ & ‘Restricted’
  23. Hyper-V Multiple Snapshot initialization is not allowed for same volumes
  24. VSS not supported for volumes with FAT32 file systems, hence during snapshot, VM will go to saved state/offline mode
  25. Live Restore, FLR and Download will fail, when the VMs have special characters in their names
  26. Cannot the abort Live Recovery when it is in progress
  27. Live Recovery cannot be performed to the same host, if the backup was configured using Vembu VMBackup Client
  28. Shielded VM properties are not recovered after restoring the VM
  29. While Log Truncation will work, Application-aware Processing will not work in Windows Server 2008 R2 guest OSes

Disk Image Backup:

  1. Disk image backup is not supported for two-digit disks, for example, Disk10, Disk11 and so on
  2. Disk image backup is not supported for ReFS, FAT and exFAT file system
  3. If the disk drives are defragmented using 3rd party tools, further incremental disk image backups will fail with CHKDSK error
  4. In disk image backup, backup schedule and drives configured for the backup cannot be modified
  5. Disk Image backup may fail to backup the encrypted partitions or files
  6. While performing Quick VM Recovery, only OS installed disk will be attached to the booted Hyper-V/KVM virtual machine
  7. Datastore created by Vembu BDR/Vembu OffsiteDR server during quick VM recovery will not be auto-removed when unmounted in Vembu console
  8. 6 GB RAM will be assigned by default for VMs booted during Quick VM Recovery in VMWare ESXi

Vembu Integration Service

  1. Vembu Integration Service will not be installed on the machine where Vembu ImageBackup Client is already installed
  2. Vembu Integration Service tray will not be available immediately after the installation
  3. Vembu Integration Service cannot be pushed to the domain machines of the same domain controller where Vembu BDR Server is installed
  4. For Windows Desktops, Voltracker driver will not be removed completely during uninstallation

File-level Recovery:

  1. File Level Recovery is supported only for NTFS file system and is not supported for other file systems such as FAT, ReFS etc
  2. File Level Recovery for the replicated VMs is supported only for NTFS, ReFS and FAT32 file systems
  3. Only volumes with NTFS file system can be recovered. This recovery will fail if compression/encryption is enabled
  4. For VMware and Hyper-V backups, File level Recovery and Disk management mount are not supported for dynamic disks
  5. For Windows disk image backup, File level Recovery is supported only for the simple volume of dynamic disks, other types of volumes such as Stripped, Spanned, Raid, and Mirrored are not supported for File Level Recovery
  6. File Level Recovery is supported only for windows virtual machines and is not supported for the other OSes such as MAC, Linux etc
  7. Folders/files encrypted in NTFS volume will not be restored when File Level Recovery is performed

Tape Backup:

  1. Abort’ and ‘Suspend’ options will not be available when tape backup and restore processes are in progress
  2. For interrupted backup jobs, data will not be deleted or resumed from where it left off; Full backup data will be copied again
  3. Multiple backups with the same name cannot be configured to tape server, where the first configured backup job will only be processed
  4. Tape backup is not supported in Vembu BDR and Vembu OffsiteDR for Linux machines
  5. Tape backup is not supported for backups from NetworkBackup clients
  6. For every schedule, full backup data is copied to tape
  7. Parallel processing for tape drivers is not supported
  8. Retention process is not available for data stored in tape media
  9. Multiple tape servers cannot be configured to a Vembu BDR or Vembu OffsiteDR server and vice versa
  10. Drive level restore is not available for disk image backup
  11. Tape backup restore fails when the target location is a network drive configured with Vembu BDR or OffsiteDR console
  12. Delete backup option will not delete backup data from tape media


  1. Multithreaded Quick VM Recovery process at the same time is not supported
  2. For VMware and Disk image backups, virtual machines created through Quick VM recovery will not contain network adapter settings, they have to enabled manually
  3. Disk Management Mount is not supported for Linux based Backup Server
  4. Folder level right-mouse-click option to mount a VHD file is disabled on Windows 2012 R2 server OS
  5. Vembu VMBackup Client tray service may fail to start after automatic software update
  6. Storing MongoDB and MySQL metadata on LVM disks are not recommended
  7. Quick booting via Hyper-V is not supported for Windows 2008 R2, Windows 2012 and Ubuntu Guest OSes with more than 2 TB disks
  8. For Vembu BDR server installed in Windows 2008 R2, following options are not supported if the guest OSes have disk size more than 2 TB: Quick VM recovery, File Level Recovery, Image Integrity Check
  9. Booting IMG files having disk size 2 TB is not supported on KVM (i.e) Linux OSes
  10. Configuring networks during Quick VM Recovery is currently supported only for Hyper-V plugin and Hyper-V Integration Services must be up-to-date for successful IP assignment
  11. Configuring networks during Quick VM Recovery is not supported in Vembu server for Windows 2008 R2 and Linux OSes
  12. Any change in disk exclusion rule for a configured backup job will be applied only when an additional full backup is scheduled
  13. Disks once excluded cannot be included back in already configured replication job
  14. If a NFS datastore is created via manual NFS share, it has be disabled before proceeding with Quick VM recovery
  15. Quick VM Recovery via Hyper-V/KVM will attach ‘Only Disk 0’ on Vembu BDR server for Windows server: 2008 R2 and Windows 2012
  16. If the ESXi is attached to vCenter then Hot Add transport mode will not work
  17. If marked chunks are deleted before performing export in BDR server, then import process will fail in OffsiteDR server
  18. Additional full backup of already seeded backup will not be considered for seed process
  19. Trying to import seed data to the offsite server with the mapped drive will fail
  20. In File-level Recovery for VMware and Hyper-V backups, volume labels (like C:\) are not shown exactly as present in source machine and are replaced with IDs such as Volume1, Volume2 etc
  21. Need to enable the “Remote Registry” service (if disabled) or make sure it is running before installing Vembu Integration Service
  22. For any client, if the repair option is interrupted, then trying the option again will result in the new client installation
  23. Tray option will not be available post automatic s/w upgrade. Restarting the machine will make the tray option available
  24. Import/export process will fail if the target location has special characters in it
  25. UEFI firmware based VMs cannot be booted in KVM using QEMU
  26. Vembu BDR Server will not perform integrity check for the backups that are encrypted using a user-generated password at standalone clients
  27. Vembu OffsiteDR will not perform integrity check for backups that are encrypted using a user-generated password created at both Vembu BDR Server and standalone clients
  28. Quick VM Recovery/Mount/Download fails for Windows XP on KVM Hypervisor
  29. Restoring persistent boot changes in Linux servers does not work
  30. Restarting VembuBDR service will make virtual drive get unlisted in file explorer, however, recovery options will work as expected
  31. Unicodes are not allowed in any kind of fields in Credential Manager, but it is allowed in VMB client and updated properly in DB
  32. There is no option to delete the added credentials, they only can be edited
  33. If Vembu Integration Service service is stopped, tray icon will not be available
  34. Emails alerts for aborted replication jobs will not have the subject stating that the replication job has been aborted
  35. In Vembu OffsiteDR Dashboard, the status of the aborted jobs will be shown as ‘Success’
Technical Support

For feedback, comments or issues, please call US: +1-512-256-8699 UK: +44-203-793-8668 or email at