Below are the links to the Update 2 cumulative binaries for 6.0.2.177 (a release specific to the DL Appliances):
Core Cumulative Patch Installer:
Rapid Recovery Core Cumulative Patch Update 2
To learn more about the patching process, please visit our patch install KB.
Defect ID | Description |
D-33763 | Protected and Replicated Agents Notification Settings are synchronized after Replication job |
D-33823 | AutoReportManagement provides broken uri for some methods |
D-33563 | Unable perform Get API request due to the restriction of the GET method length |
D-34009 | Dashboard GetInfoForAgentType API broken |
D-33570 | API function which use recovery points ID does not work because of # character |
D-33603 | VMwareProxy.Service.exe crashes with exception code 0xc0000374 on specific environment |
D-30861 | Status of replicated machine on Core Dashboard doesn't correspond to its real status |
D-33473 | Incremental archive creation fails with out of space on the target error in specific case because of incorrect space validation |
D-34331 | Unable to create archive to amazon s3 cloud to bucket in EU1 (Frankfurt) region |
D-33354 | Certificates are added to archive and useless archive certificate validation during the archive check job is performed |
D-33729 | Recovery points of 2TB full volume are not mounted from attached archive |
D-33855 | Recovery points of volume with size which can't be divided to 8192 are not mounted from attached archive |
D-33421 | Multiple duplicated e-mails are sent by core when there are several notification groups with enabled email settings |
D-27954 | Sometimes error message that appears when replication fails due to I/O problems is incorrect and misleading |
D-30629 | Server error "Object '/8199b ... 51669.rem' has been disconnected or does not exist at the server." appears when opening core and/or protected machine settings |
D-30797 | Resetting Change Block Tracking job shuts down machine instead of rebooting it in ESXi Agentless |
D-31803 | Sometimes due to specific steps which can be caused by env. issues on Exchange Agent the mountability queue is breaking which in turn breaks the export queue and it’s lead to full exports (Virtual Standby) instead the incremental |
D-32226 | Replication fails with "Unable to read data contract from stream due to incorrect RPFS file size" if metadata for problematic RP/volume was not written successfully due to environmental issues |
D-32712 | PreHyperVAgentScript should be running on the Hyper-V host during export for specific environment |
D-32938 | Linux agent could not be exported with System.InvalidOperationException: Sequence contains more than one matching element |
D-32954 | PowerShell: RecoveryPointsInfo and MasterCoreInfo properties are missing during execution get-replicatedservers command |
D-32995 | Replication fails with uninformative error message in case if response from Target were not received by Source with timeout |
D-33151 | Heartbeat is failed with error 'Unable to contact licensing server' after specific steps |
D-33168 | There is no validation during configuration retention policy with using API |
D-33541 | Protected ESXi agentless VMs eventually become locked on CWF ST environment |