BDRSuite for VMware

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. BDRSuite 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)
   • 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 BDRSuite 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 the 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 the 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
47. 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.
48. 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.
49. Manually trying to mount the disk of a synthetic merge full backup fails with the error "The file or directory is corrupted and unreadable".
50. Performing instant-boot second time for the same time-stamp fails
51. Restore Button appears for completely failed backup jobs (BDR and ODR)
52. The entire host is automatically selected if all the VMs in an ESXi host are selected manually during backup configuration
53. No alert is shown when a user edits a backup job and selects already added VMs through the vCenter. 

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.

PreviousNext