Vembu BDR Suite v4.0.2 GA- Release Notes

Vembu BDR Suite 4.0.2 is now out for production setups with enhanced performance and bug fixes.

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.2. You can perform a fresh installation or upgrade from the older version of Vembu BDR Suite to the latest v4.0.2.

What’s new in Vembu BDR Suite v4.0.2?

Vembu BDR Suite v4.0.2 is an intermediate patch update. From now you can backup up to 10 VMs for free in the full-featured free edition, previously it was limited only to 3 VMs. This release also addresses the customers reported issues and support issues of v4.0.1 along with improved stability & bug fixes.

Product Highlights

Backup & Recovery

VMware Backup & Replication – Powerful, agile and flexible data protection for your VMware VMs with agentless backup and replication.

Hyper-V Backup – Ensure complete data protection for Hyper-V VMs running on a standalone host, Hyper-V cluster SMB & CSV.

Windows Image Backup – Enhance the data protection of your Windows Servers and Workstations by backing up the entire disk or individual volumes.

File & Application Backup – Protect your data across file servers, application servers and workstations of Windows, Linux & Mac with enterprise-level functionality.

Office 365 Backup – Protect emails, contacts, calendar, and drives of Office 365 by directly backing up to Vembu Cloud.

G Suite Backup – Ensure protection of your emails, contacts, calendar, and google drives by directly backing up to Vembu Cloud.

Online Backup – Backup your files/folders and applications of Windows, Linux and Mac machines directly to the cloud, bypassing the need for a local server.

BDR360 – Get end-to-end visibility of your distributed backup infrastructure with extensive reports from a centralized monitoring portal.

Disaster Recovery

Offsite DR – Devise a reliable DR plan for your business by replicating the backup data from your on-premise data center to an offsite server.

Hybrid Cloud – Reinforce your Disaster Recovery plan by replicating the copy of backup data from your on-premise data center to Vembu Cloud.

Major features of Vembu BDR Suite

Agentless Backup & Replication

Backup & Replicate the VMs running on VMware & Hyper-V without installing any agent inside the VMs.

Changed block Tracking

Track and backup only the changes that have been made since the previous backups. Vembu has developed its own proprietary driver to track the changes made on the VMs & Physical machines.

Failover and Failback

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

Advanced Retentions Policies

The Multilevel GFS retention reduces the time taken to restore backup data and most importantly reduces the need for backup storage. It also avoids retaining long chains of incremental and helps meet the requirements of your retention policy.

Quick VM Recovery

Instantly recover the backup data as ready state VM on Microsoft Hyper-V, VMware ESXi or KVM and continue your work without any interruptions. The change made on the Quick VM session will also be recorded and can be used during the permanent recovery.

Permanent VM Recovery

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

Bare Metal Recovery

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

Advanced Reverse Incremental

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).

Native Tape Storage Support

In addition to the offsite copy, you can also archive a copy of your backup data to tape media or libraries.

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 every day.

Cross-Platform Migration

Since VMware, Hyper-V and Physical Windows Disk Image backup data are stored at the 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.

Vembu Universal Explorer

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 for free of cost after trial period.

System Requirements

Vembu BDR Backup Server

Supported Windows OS Windows Server 2019 (Standard, Datacenter),
Windows Server 2019 Core (Standard, Datacenter),
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 18.04,
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 2019 (Standard, Datacenter),
Windows Server 2019 Core (Standard, Datacenter),
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:
https://www.vembu.com/pdf/datasheet/system-requirements-datasheet.pdf
Installer Downloads

Download Vembu BDR Backup Server installer from the following URL:
https://www.vembu.com/vembu-bdr-suite-download/

Technical Documentation

Refer following URL to refer Vembu BDR Suite technical documents,
https://www.vembu.com/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 a 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 are 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 the target host, further schedules will fail
  21. If the 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 the name like * ? : | 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
  28. Quick recovery to ESXi server fails if the VM name contains : [colon] in it

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 VM 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. During Quick VM Recovery and Live VM Recovery, the Shared VHDX cannot be used as a normal disk
  13. When VMs are migrated to a new node and Vembu Integration Service is not installed in that node, then backups will fail
  14. Email Report will not be sent for Live Restore to Hyper-V in the successful completion
  15. Performing Quick VM Recovery on Hyper-V of Windows Server 2008 R2 & 2012 will attach & boot only the OS disk
  16. During a Live Recovery, VM creation will fail if the VM name or the target location has an apostrophe(‘) in it
  17. Backup of VMs with Scale-Out File Server in Hyper-V cluster will fail
  18. Hyper-V Cluster VM backup with its disks in Storage Space Direct is not supported
  19. Recovery of Generation 2 Linux OS with UEFI partition (secure boot enabled) will not work as no “.efi file” is found during the restore
  20. Backups will hang for the VMs on Windows 2008 R2 Hyper-V Host with Execution policy ‘AllSigned’ & ‘Restricted’
  21. Hyper-V Multiple Snapshot initialization is not allowed for same volumes
  22. VSS not supported for volumes with FAT32 file systems, hence during the snapshot, VM will go to saved state/offline mode
  23. Live Restore, FLR and Download will fail, when the VMs have special characters in their names
  24. Shielded VM properties are not recovered after restoring the VM
  25. While Log Truncation will work, Application-aware Processing will not work in Windows Server 2008 R2 guest OSes
  26. Prerequisites verification fails for Hyper-V standalone hosts without any alert
  27. Application aware processing is not working for the applications installed in VMs in Windows Server 2016\2019 hosts

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
  5. Agent installation progress is shown in the “Manage server” page both Hyper-V and Disk image backup, if it is of the same host

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 for the replicated VMs is supported only when Vembu BDR Server is installed on Windows and is not supported if Vembu BDR Server is installed on Linux server
  7. File Level Recovery is supported only for Windows virtual machines and is not supported for the other OSes such as MAC, Linux, etc
  8. Folders/files encrypted in NTFS volume will not be restored when File Level Recovery is performed
  9. File\Folder names will not be displayed properly in restore page for chinese language
  10. When the ‘Compressed Restore Data’ option is enabled for file-level recovery, the original files are also getting restore along with the compressed ZIP

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

General:

  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 be 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, the 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 an NFS datastore is created via manual NFS share, it has to 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. Unicode 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, the 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’
  36. While upgrading from v4.0 to v4.0.1 Vembu BDR\OffsiteDR shows an invalid alert if two instances of PostgreSQL is running in the machine
  37. Files and Folders with Turkish Characters will not be displayed correctly in view, restore, edit backup page
  38. Apache/PHP is not upgraded to the latest versions in Red Hat client builds
  39. Test connectivity is showing an improper message if a lower version of Vembu BDR server is added at the client side
  40. In some random cases, next scheduled time for the backup is not getting updated properly
  41. Unable to configure emails from Exchange Server 2016 with Authentication Enabled
  42. OffsiteDR seed is not working if the replication is configured from linux BDR server to windows OffsiteDR server due to PostgreSQL version compatibility
  43. Full featured backup configured from two servers registered to same portal account fails after License check
  44. After migrating to v4.0.2, to add more VMs to the full-featured backup job created in the previous version, refresh the page once and edit the job
Technical Support

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