Rapid Recovery 6.3 - Release Notes

Double license consumption corrected for release 6.3. Rapid Recovery Core consumes one license from your license pool per processor or CPU socket. In earlier releases, if protecting the same hypervisor in 2 Cores, twice the number of licenses were consumed. Now, if you protect guest VMs from the same VMware host in two separate Rapid Recovery6.3 Cores, only a single set of licenses from your license pool (one per socket) are consumed. Requirements: Both Cores must be part of the same Rapid Recovery License Portal group and both Cores must be version 6.3.0 or greater.

108313

Upgrade, Deploy and other web-installer dependent jobs were failing due error code: 3002. Message: "The certificate for MSI issued to Quest Software Inc is invalid."

108264

Partial backup data was not deleted from repository after failed transfer.

108098

Mount for recovery points from attached archive failed with error: 'The index xxxxxx is greater than the maximum valid index, which is one less than the capacity yyyyyy' if the volume had been shrunk.

108085

When Core service was not shut cleanly and an archive was attached, the GUI did not load, with error "Oops.. Looks like something went completely wrong."

108064

Agent protection failed with error "GetResponse timed out (stuck on collecting metadata)" on specific environment.

108006

In a specific environment, when a scheduled archive was canceled and the incomplete archive deleted, the next scheduled archive did not include the deleted recovery points, and the resulting archive could not be imported. To correct this issue, the archive structure is refreshed after a scheduled archive is canceled, and subsequent archives are valid.

107976

Scheduled archives failed, with error "Value cannot be null. Parameter name: source" after upgrade from 6.1.3 to 6.2.x.

107971

Core service hung; GUI did not load, with error "Oops.. Looks like something went completely wrong" in specific cases.

107941

Replication rate for huge base images were extremely slow due to small write buffer size on the target Core.

107933

Archive to the Amazon Glacier failed after minor network interruption due to the absence of retry logic that has subsequently been added.

107785

There was no ability to archive cluster nodes without adding cluster volumes to an archive.

107768

Rollup failed with error "cannot find the recovery point with the id __" on a system test environment.

107764

No virtual machines were displayed on the Virtual Machines page of a protected vCenter/ESXi server when a protected VM with Agent installed was added for agentless protection, and the VM was associated with its parent host.

107568

Data was lost on disk located on Scale Out File Server (SOFS) if you added some data to the disk and evicted active SOFS cluster node.

106296

Unexpected base images occurred for cloned disks during Hyper-v agentless transfers.

105606

Replication was not paused after upgrading Target Core from release 5.4.3 to release 6.2.x.

105560

Not all disks were exported after VirtualBox export of ESXi agentless VM based on Windows 8.1 x86 and Windows 8.1 x64.

103783

Core GUI would not launch after upgrade from 6.1.1 to 6.1.2 on specific environment.

102521

Azure Market Place Offer used "dell_software" in the URI.

License and copyright information for the following components (missing from release 6.2 in-product help) appears as expected in the Rapid Recovery Core in-product help topic "Third-party components":

• ANTLR 3.3.3
• bash-completion 2.1
• btrfs-tools 4.4.1
• ca-certificates 2016.10.04
• casper 1.376
• Castle Windsdor 2.5.3
• Chromium 57
• cURL 7.47
• docutils 0.14
• efibootmgr 0.12-4
• fakeroot 1.20.2
• gcc 5.3.1
• gdisk 1.0.1
• Google APIs Client Library for .NET 1.32.2
• htop 2.0.1-1
• JavaScriptEngineSwitcher 2.4.10
• jQuery 1.9.2
• Newtonsoft.Json 11.0.2, 4.0.8
• jsTree 3.1.0
• Linux-libc-dev 4.4.0
• libc6-dev-2.23
• libc-dev-bin 2.2.3
• libesdb 2015409
• libext2fs1.43.4
• libfakeroot 1.20.2
• libreadline5 5.2
• lsscsi 0.27-3
• lupin-casper 0.57
• lvm2 2.02.167
• make 4.1
• mc 4.8.15-2
• mdadmin 3.3-2ubuntu7
• Microsoft Windows Azure Storage 8.2.0
• Mono 5.2
• openssh-server 7.2p2
• Oracle ManagedDataAccess 12.2.1100
• parted 3.2-15
• PuTTy 0.70
• screen 4.3.1-2build1
• Select2 4.03
• SSH.Net 2016.1.0
• zlib 1.2.8
• python minimal 2.7.11

Additionally, this section contains substantial updates to ensure all third-party components are identified as required.

108327

For agentlessly protected machines only, web help contains a link on the protected virtual machine's System Information page that shows an incorrect topic, "Viewing system information for the Core." The link has been corrected and now points to the topic "Understanding system information for a protected machine."

Rapid Recovery 6.3 User Guide topic "Deploying a virtual machine in Azure" has been modified. It contains no unnecessary steps.

In release 6.3 and later, to export a VM to Azure, you can use an existing container or (using Advanced storage options), you can define an export container or deployment container.