Vembu BDR Suite v4.2.0 (Update 1) GA – Release Notes

Vembu BDR Suite is a comprehensive Backup & DR solution designed to protect the business-critical data across your Virtual, Physical, Cloud workloads & SaaS Applications

Gain a quick insight into the latest version of the Vembu BDR Suite v4.2.0 (Update 1) and get started with protecting your IT environment. You can perform a fresh installation of Vembu BDR Backup Server or upgrade from the older version.

What’s new Vembu BDR Suite v4.2.0 (Update 1)?

Backup support for VMware vSphere 7.0. Using Vembu BDR Suite you can backup and replicate the business critical VMs running on your latest VMware vSphere 7.0 environment.

Vembu BDR Suite v4.2.0

New Products & Features

  1. Vembu Backup for AWS EC2 instances
    • Agentless backup for EC2 instances
    • Automatic backup scheduling
    • Instance & Volume level recovery
  2. Vembu Backup for Microsoft Office365
    • Backup mailboxes, contacts, calendars and OneDrive to your data center(On-premise or any public cloud storage)
    • Backup entire domain or selected user data
    • Restore backup data to same or different user account
  3. Group Management is now available for all the users

Enhancements

  1. Enhanced the reports with more information
  2. Improved the usability of the Vembu BDR Backup Server & Offsite DR Server GUI
  3. Improved error messages & alert notifications
  4. Vembu Universal Explorer is installed with the Vembu BDR Backup server & Offsite DR Server installation. It can be accessed easily using on-screen instruction when clicking on the Application Item-level Recovery option
  5. Vembu BDR360 agent is installed with the Vembu BDR Backup server & Offsite DR Server installation

Along with the new features and Enhancements, Vembu BDR Suite v4.2 also addresses the customers reported issues and support issues of the previous version of vembu along with improved stability, performance & bug fixes.

Licensing & Pricing updates

Along with the new products, features, and enhancements, Vembu BDR Suite v4.2 also brings some changes in its licensing and pricing.

  • The license cost of Vembu Backup for Microsoft Windows(Windows Servers) is reduced to $60/Server/Year from $120/Server/Year
  • The number of workstations that can be backed up under the Free Edition is reduced from unlimited workstations to 10 workstations
  • The users should pay $15 /Workstation/Year to backup their Windows workstations at image-level with Vembu Backup for Microsoft Windows
  • The users should pay $15 /Workstation/Year to backup their Windows & Mac workstations at file-level with Vembu Backup for File & Application
  • The free edition of the Vembu Cloud Backup for Files & Application (Vembu Online Backup) is now discontinued
  • The users should pay $6/Workstation/Year to backup their Windows & Mac workstations at file-level with Vembu Cloud Backup for File & Application
If you have queries with the pricing, you can reach our sales team at vembu-sales@vembu.com to clarify your queries.

Vembu BDR Suite of Products

Backup & Recovery

Vembu Backup & Replication for VMware

Agentless, application-aware Backup & Replication for VMware VMs with Instant Recovery at VM, File and Application-level

Vembu Backup for Microsoft Hyper-V

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

Vembu Backup for Microsoft Windows

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

Vembu Backup for File & Application

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

Vembu Backups for AWS

Simple, secure and cloud-native backup solution for your AWS EC2 instances. You can recover your backup instance, volume or even files at any time with near-zero RTO.

Vembu Backup for Microsoft Office 365

Protect emails, contacts, calendar, and drives of Office 365 by directly backing up to your datacenter.

Vembu Backup for Google G Suite Beta

Ensure protection of your emails, contacts, calendar, and google drives by directly backing up to your datacenter.

Vembu Cloud Backup for File & Application

Backup your files/folders and applications of Windows, Linux and Mac machines directly to Vembu Cloud, bypassing the need for a local storage.

Vembu Cloud Backup for Microsoft Office 365 Beta

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

Vembu Cloud Backup for Google G Suite Beta

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

Offsite Copy/Disaster Recovery

Vembu Offsite DR

Devise a reliable DR plan for your business by replicating the backup data from your on-premise BDR Backup Server to an offsite datacenter or any public clouds.

Vembu Cloud DR

Reinforce your Disaster Recovery plan by replicating the copy of backup data from your on-premise BDR Backup Server to Vembu Cloud.

Management & Monitoring

Vembu BDR360 Cloud

Get end-to-end visibility of your distributed backup infrastructure anywhere and anytime with extensive reports from a centralized monitoring.

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
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 v53 & above and Chrome v68 & above
Note: The minimum requirement of 8 GB RAM and Quad-Core processor is only for the evaluation purpose. For production deployment, it is recommended to install Vembu BDR Backup Server in a machine with 16 GB RAM and Octa-Core processor for optimum performance.

For more details on system requirements and supported platforms, please refer to the following 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 & Recovery

  1. VMware backup does not support backup of virtual machines with independent disks
  2. Application-aware backup is not supported for 32 bit Windows Guest OS and Linux VMs
  3. Vembu VMBackup does not support backup of 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 & below
  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. Dynamic disks can only be recovered through Full VM Recovery to ESXi
  22. In Disk level recovery, if the target VM does not support SATA controller, SATA disks will be restored as SCSI disk
  23. Instant Boot VM 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. New disk attached will not be reflected while performing Instant Boot VM to ESXi for that schedule
  27. Instant Boot VM to ESXi server fails if the VM name contains : [colon] in it
  28. If the backup was completed with any warnings message related to Oracle application-aware processing, then the backup report is unable to show the full Oracle warning message, it will be available only in the log files
  29. If the Oracle database is in begin backup mode before backing up the VM, then that database turns to end backup mode automatically after the completion of the successful backup
  30. Backup fails with the error “Failed to perform pre-backup steps” if the Application-aware is enabled for the Oracle 11gR2 running on Windows 2008r2 VM
  31. Need to manually alter database from begin backup to end backup, if the backup is aborted, suspended, or the VembuBDR service restarted or stopped
  32. Failed to change the mode of oracle database to ‘End Backup’ while performing Instant Boot VM and Full VM Recovery to ESXi host
  33. The backup will fail if the pagefile.sys or hiberfil.sys file is excluded from the VM disk of type FAT32
  34. NOARCHIVELOG oracle database is not supported for application aware processing
  35. Oracle’s Real Application Clusters (RAC) and Automatic Storage Management (ASM) are not supported
  36. Oracle servers using Data Guard are not supported
  37. Different versions of Oracle Database deployed on the same server are not supported
  38. The 32-bit version of Oracle database is not supported
  39. Granular Level recovery for Oracle database is not supported
  40. The user had to manually select the available proxy during backup job configuration. Automatic Proxy selection is not supported
  41. Windows Server OSes with 64-bit architecture can be used as a proxy. (Other OS architectures are not supported)
  42. A single proxy can process up to 5 backup jobs simultaneously
  43. Transport mode selection is not provided in UI
  44. Only a single proxy can be used for a particular backup job. Multiple Proxy is not supported
  45. Backup is getting hanged if network connection is dropped during Pre-Backup steps
  46. VMware backup will fail when the VMs configured via vCenter Server of v6.7 U 3B where ESXi Host’s version is lower than v6.7 U 3B

VMware VM Replication

  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
  12. VM replication/Restore using proxy is not supported

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. Full VM Recovery of 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 Instant Boot VM will not be auto-removed when unmounted in Vembu console
  11. 6 GB RAM will be assigned by default for VMs booted during Instant Boot VM in VMWare ESXi
  12. During Instant Boot VM and Full 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 Full VM Recovery to Hyper-V in the successful completion
  15. Performing Instant Boot VM on Hyper-V of Windows Server 2008 R2 & 2012 will attach & boot only the OS disk
  16. During a Full VM Recovery, VM creation will fail if the VM name or the target location has an apostrophe(‘) in it
  17. Hyper-V Cluster VM backup with its disks in Storage Space Direct is not supported
  18. Recovery of Generation 2 Linux OS with UEFI partition (secure boot enabled) will not work, if no .efi file is found during the restore
  19. Backups will hang for the VMs on Windows 2008 R2 Hyper-V Host with Execution policy ‘AllSigned’ & ‘Restricted’
  20. Hyper-V Multiple Snapshot initialization is not allowed for same volumes
  21. VSS is not supported for volumes with FAT32 file systems, hence during the snapshot, VM will go to saved state/offline mode
  22. Full VM Recovery, File Level Recovery and Download VMs will fail, when the VMs have special characters in their names
  23. Shielded VM properties are not recovered after restoring the VM
  24. While Log Truncation will work, Application-aware Processing will not work in Windows Server 2008 R2 guest OSes
  25. Prerequisites verification fails for Hyper-V standalone hosts without any alert
  26. VMs running on the Hyper-V host of Windows Server 2016 nano servers are not supported for backup
  27. Backup fails if the VM disks configured for backup are compressed
  28. If the VMs configured for backup from Hyper-V host of Windows Server 2012R2 are upgraded to Windows Server 2016, then the very first checkpoint created after OS upgrade for the VM backup progress will not be removed automatically
  29. If new disks were added to the VMs during an incremental backup or if VM has a differencing disk, then the backup will be processed for the entire disk but upload only the used space
  30. You cannot add a cluster to the backup infrastructure if the Hyper-V Cluster name has more than 14 characters. However, the Hyper-V Cluster can be added using the cluster IP
  31. Changes tracking using Microsoft native RCT is only supported for Windows Server 2016, Windows Server 2019 and Windows 10
  32. Only the Virtual machines with hardware version 6.2 above support changed tracking using Microsoft native RCT. Lower hardware versions of the virtual machine will be backed up using a checksum
  33. Pass-through virtual disks and disks connected inside the guest VM via iSCSI will be skipped from backup processing
  34. Shared VHDX/VHDS VM environments not supported for backups using Microsoft native RCT
  35. Backup fails if the VM disks configured for backup are encrypted
  36. If the virtual machine reverted to older checkpoints after that VM was successfully backed up, the next immediate schedule will proceed using the checksum
  37. While performing Instant Boot VM and Full VM Recovery Linux VM of Generation 2, then it is required to import VM configuration file available in the location “sgstorage -> -> -> 1 -> -> -> -> 1-500 -> 1″ to the restore location to avoid boot failure
  38. Any new node is added or an older node removed from the cluster then the immediate backup schedule is based on checksum
  39. Any node in the cluster goes unreachable in between two or more backup schedules then the immediate backup schedule is based on checksum
  40. If the VM’s virtual hard disk is disconnected and reconnected in Hyper-V host, then the next immediate schedule is based on checksum
  41. Backup is getting hanged if network connection dropped when processing the VM Configuration file

Disk Image Backup

  1. Disk image backup is not supported for ReFS, FAT and exFAT file system
  2. If the disk drives are defragmented using 3rd party tools, further incremental disk image backups will fail with CHKDSK error
  3. In disk image backup, backup schedule and drives configured for the backup cannot be modified
  4. Volumes encrypted using bitlocker are not supported for backup
  5. While performing Instant Boot VM, only OS installed disk will be attached to the booted Hyper-V/KVM virtual machine
  6. Datastore created by Vembu BDR/Vembu OffsiteDR server during Instant Boot VM will not be auto-removed when unmounted in Vembu console
  7. 6 GB RAM will be assigned by default for VMs booted during Instant Boot VM 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 systems 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 the 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 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. 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 backup jobs with the same name cannot be configured to tape servers. Only the first configured backup job will 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 Instant Boot VM process at the same time is not supported
  2. For VMware and Disk image backups, virtual machines created through Instant Boot VM option will not contain network adapter settings, they have to be enabled manually
  3. Disk 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. Instant boot VM via Hyper-V is not supported for Windows 2008 R2, Windows 2012 and Ubuntu Guest OSes with more than 2 TB disks
  8. The Vembu BDR Backup servers installed in Windows 2008 R2 do not support Instant Boot VM, File-Level Recovery, Image Integrity Check for guest OSes having disk size more than 2 TB
  9. Booting IMG files having disk size 2 TB is not supported on KVM (i.e) Linux OSes
  10. Configuring networks during Instant Boot VM 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 Instant Boot VM 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 Instant Boot VM
  15. Instant Boot VM 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 the import process will fail in OffsiteDR server
  18. Additional full backup of already seeded backup will not be considered for seed process
  19. 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
  20. Need to enable the “Remote Registry” service (if disabled) or make sure it is running before installing Vembu Integration Service
  21. Tray option will not be available post automatic s/w upgrade. Restarting the machine will make the tray option available
  22. Import/export process will fail if the target location has special characters in it
  23. UEFI firmware based VMs cannot be booted in KVM using QEMU
  24. Vembu BDR Server will not perform integrity check for the backups that are encrypted using a user-generated password at standalone clients
  25. 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
  26. Instant Boot VM/Disk Mount/Download VMs fails for Windows XP on KVM Hypervisor
  27. Restoring persistent boot changes in Linux servers does not work
  28. Restarting VembuBDR service will make virtual drive get unlisted in file explorer, however, recovery options will work as expected
  29. Unicode are not allowed in any kind of fields in Credential Manager, but it is allowed in VMB client and updated properly in DB
  30. There is no option to delete the added credentials, they only can be edited
  31. If Vembu Integration Service service is stopped, the tray icon will not be available
  32. Emails alerts for aborted replication jobs will not have the subject stating that the replication job has been aborted
  33. In Vembu OffsiteDR Dashboard, the status of the aborted jobs will be shown as ‘Success’
  34. While upgrading from v4.0 to v4.01/v4.0.2 Vembu BDR\OffsiteDR shows an invalid alert if two instances of PostgreSQL are running in the machine
  35. Apache/PHP is not upgraded to the latest versions in Red Hat client builds
  36. In some random cases, the next scheduled time for the backup is not getting updated properly
  37. Unable to configure emails from Exchange Server 2016 with Authentication Enabled
  38. OffsiteDR seed is not working if the replication is configured from linux BDR server to windows OffsiteDR server due to PostgreSQL version compatibility
  39. Full featured backup configured from two servers registered to the same portal account fails after License check
  40. After doing seed migration to the Offsite DR server, the first incremental restore point is not getting listed in the recovery page, until the second incremental backup is successfully sent to the OffsiteDR server
  41. If the redistributable package was skipped during the installation, in case if it is manually removed or an Antivirus cleans up the package from the temp location, the installation will not throw any error and will be completed successfully
  42. The customization of port values during the installation is not supported for client agents
  43. System files exclusion is not working for simple dynamic disks
  44. File exclusion for image backup is supported only for Microsoft Windows NTFS volumes
  45. Split, spanned or mirrored volumes of dynamic disks are not supported for file exclusion
  46. File exclusion will not work if the VM migrates from one host to another
  47. The backup will fail if the pagefile.sys or hiberfil.sys file is excluded from the VM disk of type FAT32
  48. Historical vm level report doesn’t show the warning remarks for VMware plugin on both Windows & Linux BDR servers
  49. When backing up Linux VMs in turned off state, the backup job level report status and remarks are different from list backup jobs and recovery page reports
  50. If a single VM is configured for backup in a backup job, and it completes with a warning, but the backup job level report is updated incorrectly as ‘Failed’ instead of ‘Warning’
  51. In a VM backup job, if 1 or more VM backup is completed with warning and rest are successful. then the backup job level report updated incorrectly as ‘Partial’ instead of ‘Warning’
  52. When backing up Linux VMs in turned on state, the backup job level report status and remarks are different from list backup jobs and recovery page reports
  53. If the VM name is changed after configuring the backup, then Data integrity report displays only the old VM name instead of new name
  54. When editing the backup job, selecting the “Run this backup job immediately after saving” checkbox will not run the backup job immediately
  55. Resume restore option is not supported for suspended restores of File\Folder backups
  56. There is no option to filter and view only missed schedules in backup job level report page
  57. Interrupted server rebuild process will not proceed from where it left off
  58. For boot failure cases, the boot status will be shown as ‘Success’ in data integrity report
  59. End time of Data Integrity Check is incorrect in Data Integrity Reports for backup jobs which have more than one VM
  60. After upgrading the BDR360 agent, the reports are not sending to BDR360 Server
  61. For file/folder backup, if the backup schedule has no new or modified files, but the backup server shows ‘Backup completed successfully’ in the report instead of ‘No new or modified files found for backup’
  62. VMware & Hyper-V virtual appliances for Vembu BDR Backup Server and Vembu Offsite DR Servers are retired

AWS Backup

Limitation

  1. Backing up instances across different regions of an AWS Account in the same backup job is not supported
  2. For Pre/Post-script enabled backups, the instance should have both pre- and post- scripts. If scripts are given for only one case (before or after), then the backup job will fail
  3. Restore will fail, if the backed up instance’s keypair or Security group, subnet or vpc is not found

Known Issues

  1. Vembu Integration Service fails to start after system reboot in Ubuntu 18.04
  2. The backup job fails with the error “Not enough license units are available in the backup server”, even though the unassigned licenses (Free and Standard) are available in your portal account. We recommend you perform a Run License Check after which the backup job will be successful
  3. For instances that have partially successful backups, backup retention will not happen
  4. Once we changed the Vembu BDR Backup Server edition to free edition will reflect in the backups only after performing the Run License Check

Microsoft Office 365 Backup

Limitation

  1. Modified and deleted emails are not be tracked during the incremental backup
  2. Version information is not available for calendar backup
  3. Deleted emails are not tracked and are not excluded during restore
  4. Email items will be restored only as a draft in the mailboxes
  5. Tree view not available for mailbox folder and Onedrive folder
  6. Attachments alone cannot be viewed or downloaded in the mail view
  7. The Domain with Multi Factor Authentication(MFA) is not supported for backup

Known Issues

  1. Email count & size information are not updated properly in the backup report if the application is stopped when the backup is in progress
  2. Deleted backup job data is removed from the backup repository
  3. Last modified time of the calendar event is displayed in the calendar view of the particular backup
  4. Failure status will not be updated in the backup report when the application is stopped or restarted when the backup is in progress
  5. Sub folders will not be recovered while choosing root folder during OneDrive Recovery
  6. Backup will run only if the license is applied to all users after the portal registration
  7. Some of the properties of contacts are not being recovered during contact restore
  8. There is no option provided in web console to delete added Office 365 domain for backup
  9. Contacts from deleted contacts, groups, default global address list, all rooms, all Users will not be backed up
  10. CC and BCC recipients informations are not displayed in mail view during recovery