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 the 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 the Vembu server for Windows 2008 R2 and Linux OSes
  12. Any change in the 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 the 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 the BDR server, then the import process will fail in the OffsiteDR server
  18. Additional full backup of already seeded backup will not be considered for the seed process
  19. In File-level Recovery for VMware and Hyper-V backups, volume labels (like C:\) are not shown exactly as present in the 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. The 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 the VembuBDR service will make the 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 the 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 a 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 a 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 is updated incorrectly as ‘Partial’ instead of ‘Warning’
  52. When backing up Linux VMs in a 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 the Data integrity report displays only the old VM name instead of the 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 on backup job level report page
  57. The 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 the 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
  63. All the recovery points are listed in the ODR restore tree if the retention for the backup job happens and then replicated to the Offsite DR server.
  64. The remark of the backup job level report updated incorrectly, if the backup job fails due to no space in the volumes of the backup repository.

NextPrevious