BDRShield Known Issues & Limitations

BDRShield Known Issues & Limitations

This document will provide detailed information about the known issues and limitations of each module, helping you identify potential challenges and implement effective workarounds to ensure uninterrupted operations.

File & Folder Backup & Recovery (Windows/Linux/Mac/NAS)

  1. File Level Recovery is supported only for the 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 the NTFS file system can be recovered. This recovery will fail if compression/encryption is enabled.
  4. For VMware/Hyper-V/Proxmox, File-level Recovery works with Simple, Striped, and Mirrored volumes on Dynamic Disks. Instant Boot and Full VM Recoveries are also supported. The Disk Mount option is not available 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 BDRShield Backup Server is installed on Windows and is not supported if BDRShield Backup Server is installed on the 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 on the restore page for the 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
  11. The File & Folder Backup (for Endpoints) does not support parallel backup jobs. Only one backup job can be performed at a time for each endpoint.

Windows Disk-Image Backup & Recovery

  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. Disk Image backup may fail to backup the encrypted partitions or files
  5. While performing Quick VM Recovery, only OS installed disk will be attached to the booted Hyper-V/KVM virtual machine
  6. Datastore created by BDRShield Backup Server/ OffsiteDR server during quick VM recovery will not be auto-removed when unmounted in console
  7. 6 GB RAM will be assigned by default for VMs booted during Quick VM Recovery in VMWare ESXi
  8. If the backup job is interrupted & if the disk configured for the backup is extended after interruption. BDRShield Backup Server Service is getting stopped if the backup job is continued from where it left off after the interruption.
  9. Incremental backup of the OS drive fails if the file exclusion is enabled.

Microsoft 365 Backup & Recovery

  1. Deleted emails are not tracked and are not excluded during the restore
  2. Tree view not available for mailbox folder and OneDrive folder
  3. Attachments alone cannot be viewed or downloaded in the mail view
  4. The Domain with Multi-Factor Authentication(MFA) is not supported for backup
  5. Email count & size information are not updated properly in the backup report if the application is stopped when the backup is in progress
  6. The last modified time of the calendar event is displayed in the calendar view of the particular backup
  7. Subfolders will not be recovered while choosing the root folder during OneDrive Recovery
  8. Some of the properties of contacts are not being recovered during contact restore
  9. Contacts from deleted contacts, groups, default global address list, all rooms, all Users will not be backed up
  10. CC and BCC recipients information are not displayed in mail view during recovery
  11. Editing a backup job and including the Group Mailbox backups up ‘Group Conversation’ data instead of ‘Group Drive’ data alone.
  12. The names of the Teams-Channel files which are renamed are not getting reflected during the successive incremental schedules. During the restore, the files are restored with an older name.
  13. BDRShield Backup Server service stops during the backup schedule if one or more storage volumes in the particular storage repository is disconnected.
  14. Performing ‘Delete All’ does not remove the Microsoft 365 & Google workspace backup jobs from the BDRShield Backup Server.
  15. If there are more than 10 incremental schedules for a backup job then the full-backup report not displaying on historical-report and the total schedule count also displays incorrectly.
  16. Even after the completion of the backup job, the status of the job is still shown as ‘Backup In Progress’, only after the refresh status is updated to idle.
  17. The email forwarded (or) replied to another user account is backed up twice during the incremental schedule.
  18. Wrong backup job reports remark, if the backup fails due to no storage space in the repository.
  19. Sharepoint site page templates, restore is not working
  20. Performing subsite restore to “original site” restore the data to the new site instead of restoring data to the original site

Google Workspace Backup & Recovery

  1. After save/update Web Proxy settings, the GSuite Agent service has to be restarted to reflect those changes.

VMware Backup & Replication

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 Windows Guest OS and Linux VMs
  3. BDRShield 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 the 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 the appropriate block size given below, depending on the maximum disk size of the source VM(s)
    1. 1MB block size – Support up to 256GB
    2. 4MB block size – Support up to 1024GB
    3. 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. Re-IP settings is not supported for Linux guest OSes and only supported for Windows Guest OS
  12. Application-aware backup requires administrator privileges of OS drive agent installation
  13. Backup/Replication of Encrypted VMs in vSphere host v6.5 is not supported
  14. Backup/Replication of VM name with special characters { } will fail with a modular exception error
  15. Backup/Replication of VMs may fail with “VMware Modular exception error” if there is compatibility/permission issue with the ESXi and the respective vCenter
  16. Backup/Replication of VMs with special character {} in configuration files or file/folder path will fail
  17. If SSL is not enabled for a particular host, backup and restore are not possible
  18. Replication will fail if the target ESXi host’s datastore is renamed in between schedules
  19. If the replicated VM is deleted from the target host, further schedules will fail
  20. Dynamic disks can only be recovered through Full VM Recovery to ESXi
  21. In Disk level recovery, if the target VM does not support SATA controller, SATA disks will be restored as SCSI disk
  22. Instant Boot VM to Hyper-V Manager of VM whose boot disk is SATA is not supported
  23. Dynamic disks can only be recovered through Live recovery to ESXi
  24. Image integrity check for VMs with GPT as boot disk is not supported for Guest OS less than Windows 2012
  25. New disk attached will not be reflected while performing Instant Boot VM to ESXi for that schedule
  26. Instant Boot VM to ESXi server fails if the VM name contains : [colon] in it
  27. 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
  28. 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
  29. 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
  30. Need to manually alter database from begin backup to end backup, if the backup is aborted, suspended, or the BDRShield service restarted or stopped
  31. Failed to change the mode of oracle database to ‘End Backup’ while performing Instant Boot VM and Full VM Recovery to ESXi host
  32. The backup will fail if the pagefile.sys or hiberfil.sys file is excluded from the VM disk of type FAT32
  33. NOARCHIVELOG oracle database is not supported for application aware processing
  34. Oracle’s Real Application Clusters (RAC) and Automatic Storage Management (ASM) are not supported
  35. Oracle servers using Data Guard are not supported
  36. Different versions of Oracle Database deployed on the same server are not supported
  37. The 32-bit version of the Oracle database is not supported
  38. Granular Level Recovery for Oracle database is not supported
  39. The user had to manually select the available proxy during backup job configuration. Automatic Proxy selection is not supported
  40. Windows Server OSes with 64-bit architecture can be used as a proxy. (Other OS architectures are not supported)
  41. A single proxy can process up to 5 backup jobs simultaneously
  42. Transport mode selection is not provided in UI
  43. Only a single proxy can be used for a particular backup job. Multiple Proxy is not supported
  44. Backup is getting hanged if the network connection is dropped during Pre-Backup steps
  45. 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
  46. If there are multiple VMs in a backup job, aborting the backup job will display the only details of the VMs which are in progress in the client-side report page, whereas the detail of the VMs for which the backup is Yet to start is not getting displayed.
  47. The difference in GFS merge is observed if the GFS retention policies of the backup job are edited and saved. GFS full marked restore is not considered as a version if there are no further increments to it.
  48. Manually trying to mount the disk of a synthetic merge full backup fails with the error “The file or directory is corrupted and unreadable”.
  49. Performing instant-boot second time for the same time-stamp fails
  50. Restore Button appears for completely failed backup jobs (BDR and ODR)
  51. The entire host is automatically selected if all the VMs in an ESXi host are selected manually during backup configuration
  52. No alert is shown when a user edits a backup job and selects already added VMs through the vCenter.

VMware 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. The Re-IP Mapping option is not supported for VM Replication in Linux-based Backup Servers.
  12. VM replication/Restore using a proxy is not supported.

Microsoft Hyper-V Backup & Replication

Microsoft 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 that 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 of 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 BDRShield Backup Server/ OffsiteDR server during Instant Boot VM will not be auto-removed when unmounted in 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 BDRShield 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 the 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 the 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
  42. Hyper-V VM backup using RCT fails if the guest VM is Windows Server 2008 R2
  43. If the Hyper-V VM property “quality of service” is changed, then the property changes are not replicated to the replica VM

AWS Backup & Recovery

  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.
  4. BDRShield Integration Service fails to start after system reboot in Ubuntu 18.04
  5. 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
  6. For instances that have partially successful backups, backup retention will not happen
  7. Once we changed the BDRShield Backup Server edition to the free edition will reflect in the backups only after performing the Run License Check.
  8. The backup job is getting hanged if the backup job is scheduled when SSM service is stopped.

KVM Backup and Recovery

  1. Backup functionality is limited to VMs using the QCOW2 disk format. Raw disk backups are not supported.
  2. Backup operations are only available for running VMs. VMs that are powered off cannot be backed up.
  3. Newly added disks during incremental backups will only be included in the next full backup cycle, not in the current incremental backup.
  4. Application-aware backups are not currently supported.
  5. The ability to create backup copies is not available.
  6. Parallel backups at the VM and disk level are not supported. However, backup-level parallelism is available for improved performance.
  7. Live recovery is only supported for file-level storage. Block-level storage is not supported for live recovery.

Ovirt Backup and Recovery

  1. Backup functionality is limited to VMs using the QCOW2 disk format. Raw disk backups are not supported.
  2. Backup operations are only available for running VMs. VMs that are powered off cannot be backed up.
  3. Newly added disks during incremental backups will only be included in the next full backup cycle, not in the current incremental backup.
  4. Application-aware backups are not currently supported.
  5. The ability to create backup copies is not available.
  6. Parallel backups at the VM and disk level are not supported. However, backup-level parallelism is available for improved performance.
  7. Live recovery is only supported for thick-provisioned disks.

Proxmox Backup and Recovery

  1. Backup operations are only available for running VMs. VMs that are powered off or in a paused state cannot be backed up.
  2. Application-aware backups are not currently supported.
  3. The ability to create backup copies is not available.
  4. Parallel backups at the VM and disk level are not supported. However, backup-level parallelism is available for improved performance.
  5. Live recovery is only supported for file-level storage. Block-level storage is not supported for live recovery.

Tape Archives

  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 BDRShield Backup Server and 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. The retention process is not available for data stored in tape media
  9. Multiple tape servers cannot be configured to a BDRShield Backup Server or 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 BDRShield Backup Server or OffsiteDR console
  12. Delete backup option will not delete backup data from tape media

BDR 360 Server

  1. BDR360 Server installation is supported only for Windows machines (Linux BDR360 Server is not supported). The supported OSes are Windows 10 and above, Windows Server 2012 R2 and above.
  2. Report sync from Offsite DR to BDR360 server is not supported
  3. Report sync from Linux BDR to BDR360 Server is not supported
  4. Report sync is applicable only for image and file based backups such as VMware/Hyper-V/Windows & FileServers/Endpoints/Applications and not for AWS backup & Office365 Backups.
  5. Need an option to change the MBS server ip in the backup server, if the ip changed for MBS server
  6. If we disable the MBS from the BDR server, CPU alone increased from 40% to 60% after disabling the MBS. Also it decreased gradually from 60% to 0% in 15 minutes.
  7. MBS : There is a possibility for the report loss in MBS server, if worklist file creation failed in BDR Server
  8. MBS: Need to grayed out the Boot Preview icon in Data integrity Reports.
  9. MBS : The file based backups are listing in the protected Hosts/VMs page
  10. BDR 360 – View Host Information and Report option is not available for DI backup in “Protected Host Page”
  11. In all reports page, if we download a particular server report using global filter, the downloaded reports are not based on the selected server, its downloading all servers report
  12. MBS : Faced CPU fluctuation issue between 70% to 100 % in MBS server. Also the Max CPU used by psql process freed up immediately.
  13. MBS : After MBS server installation the shortcut name is “Vembu BDR Server”. Need to change the shortcut name related to BDR360 server.
  14. As a user I should have an option to do the testconnectivity between MBS and BDR Backup Server
  15. MBS : In VembuBDR360Agent log, the most of the logs prints are shown as “Error” for success prints.
  16. Need an option to manage the BDR server such as activate, deactivate, health status and delete server  in the MBS server.
  17. MBS : Whether the Criteria Based Email Notification is applicable for MBS server.
  18. Machine name and Host information’s are not available for unprocessed backup jobs in “Protected Hosts” page
  19. Reports are not pushed to MBS server, if we stop and restart the MBS PSQL Service.
  20. MBS : In Linux BDR, after the Intermittent bulk push, some reports are not synced properly. In psql error log, getting the warning with ” worker took too long to start; canceled”.
  21. MBS : List of Tape Archive Jobs page are not shown based on the server specific filter rule enabled in global filter settings. For a non-configured tape backup server, the text “No Tape Archive jobs configured” is not available.
  22. Empty report is downloading, if we download the VM List Historical reports.
  23. In MBS, Duplication of backup jobs are listed in the Host/VM Backup Dashboard page.

BDRShield Integration Services

  1. BDRShield Integration Service will not be installed on the machine where ImageBackup Client is already installed.
  2. BDRShield Integration Service tray will not be available immediately after the installation.
  3. BDRShield Integration Service cannot be pushed to the domain machines of the same domain controller where the BDRShield Backup Server is installed.
  4. For Windows Desktops, the 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.

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. 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 BDRShield 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 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 BDRShield Backup 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 BDRShield 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. BDRShield Backup Server will not perform integrity check for the backups that are encrypted using a user-generated password at standalone clients
  25. OffsiteDR will not perform integrity check for backups that are encrypted using a user-generated password created at both BDRShield Backup 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 BDR 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 BDRShield 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 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 BDRShield Backup Server\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 BDRShield Backup Server and BDRShield 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.
  65. If the Linux users of BDRShield wish to upgrade from any of the previous versions i.e. v5.0.0/ v5.0.0 U1/ v5.0.0 U2; to the new v5.1, then they must first upgrade to v5.0.0 U3 and later to v5.1 of the BDRShield (Linux build).
  66. In BDRShield v5.1 (BDR Backup Server/ Offsite DR Server) only one tape server can be added.