Each product is immediately available as a separate download from the Cristie Licensing portal download area.
Common to all BMR products
- The online licensing option has been retired (Windows & Linux)
- The legacy Automated DR Answerfile Tool has been retired (Windows)
- A corrupt license file causes the run of xBMRCFG.exe to hang. A corrupt license file no longer causes the exe to hang. (Windows)
- During a DR sequence it is now possible to add multiple DNS servers to post-recovery networking. (Linux)
- The XBMR DR environment now requires a minimum of 6GB RAM to operate correctly. (Linux)
- The selection/de-selection of disks/volume groups/file systems during a DR sequence has been improved to better handle large quantities of such items. (Linux)
- Some files were left behind when uninstalling BMR products from a host. This is now fixed. (Linux)
- The ‘Show Logfiles’ option in Linux XBMR shows no files after a DR. This is now fixed (Linux)
- The gateway is now a mandatory field when configuring a static IP on the Post Recovery Network configuration screen. (Linux)
- Other minor bug fixes and improvements.
- A Windows Server 2016 recovery to a vSphere target where the SCSI Controller has been set to VMWare Paravirtual would fail to boot due to an ‘INACCESIBLE_BOOT_DEVICE’ error. This is now fixed.
- CBMR now excludes DropBox and OneDrive contents from a backup.
- Now supports VTD backups larger than 2TB.
- A backup to TSM fails with “Couldn’t open backup location SMERR_NO_SUCH_DEVICE”. This is now fixed. (Linux)
- CoBMR now unregisters sources/targets from the server if the IP matches the current recovery environment.
- A recovery of a block-based backup fails if hostname in the DR environment is changed before recovery. This is now fixed.
- CoBMRCfg.exe hangs if ‘M-Files’ software is installed on the host. This is now fixed.
- The install of CoBMRCfg.exe fails on Win2008R2. This is now fixed.
- Cohesity Multi-tenancy recovery not working. This is now fixed.
- Restoring a registered source with no active protection job on the server throws you back to the CoBMR DR settings page without explanation. This is now fixed.
- The XBMR DR environment incorrectly refers to a ‘Cohesity VE server’ instead of ‘Cohesity DataProtect Server’. This is now fixed (Linux)
- An XBMR DR recovery would sometimes fail with “Failed to make machine bootable.”. This is now fixed (Linux)
- With XBMR during a DR sequence, the get config step throws up a Firefox warning. This is now fixed. (Linux)
- With XBMR during a DR sequence, failed jobs still show when filtering out backups with warnings. This is now fixed. (Linux)
- With XBMR during a DR sequence, using SSL verify checkbox causes previously entered fields to get reset. This is now fixed. (Linux)
- With XBMR during a DR sequence, a point in time recovery via the Cristie Virtual Appliance (VA) results in incorrect Epoch time conversion to milliseconds . This is now fixed. (Linux)
- Improved the clarity of any SSL error messages reported during an XBMR DR sequence. (Linux)
- NBMR installation log files did not show the reason for failure during a silent install. This is now fixed.
- NBMR 9.3.2 PE10 recovery of a 2019 EFI Dell EMC NetWorker™ client backup undertaken from the client, hangs on the Volume Layout screen. This is now fixed.
- TBMRCFG.exe hangs if run on Windows 10 with a bit-lockered O/S disk. This is now fixed
- During an XBMR DR sequence doesn’t show the date of a selected backup. This is now fixed (Linux)
Note: These BMR products are compatible with the Cristie VA 4.3 release and you will see an update now.