The following is a list of enhancements implemented in Rapid Recovery6.8.
Table 1: General enhancements
| Enhancement | Issue ID |
|---|---|
| Supports new kernels using new Linux OS for version 5.8 and higher | RR-110932 |
| Add support of VMware vSphere 8 | RR-111263 |
| Security fixes in 6.8 | RR-111265 |
| RHEL, Oracle, Alma, Rocky Linux 9 support | RR-111269 |
| Ubuntu 22.10 support | RR-111272 |
| Live DVD based on Ubuntu 23.04 | RR-111273 |
The following is a list of operating systems and applications that have limited support due to end-of-life status as of Rapid Recovery 6.8:
The following applications are no longer support by Rapid Recovery as of release 6.8:
The following table includes a list of issues addressed in this release.
Table 2: Issues resolved in this release
| Issue Description | Issue ID |
|---|---|
| Upgrade, Deploy, Installation with web-installer are failing due error code: 3002. Message: The certificate for xxx_x64.msi issued to Quest Software Inc. is invalid: The certificate is revoked. | 111431 |
| Upgrading the agent to version 6.8 causes backups to fail for CentOS 7.X machines | 111389 |
| Agentless backups failing for Windows machines on specific environment | 111388 |
| 'Password' field is absent in Import Archive Wizard in Chrome | 111381 |
| BMR for Linux Agentless VM fails with error: GetAttachedDevices failed to return a proper list of devices, error code NoEntry | 111380 |
| Windows 2012 R2 cannot boot after the agent upgrade to 6.8 | 111379 |
| fix_boot.sh script does not work on SLES 15 | 111378 |
| Very old versions of UltraVNC shown in tooltips | 111377 |
| VirtualBox export is failing for all agent and OS types with error "Input string was not in a correct format" | 111376 |
| BootCD with VNC creation fails with Error Unable to load DLL 'D3Des.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) | 111375 |
| LMU cannot be opened | 111364 |
| Agent x32 service fails to start | 111363 |
| PS commands fail with "Could not convert from 'Replay.Common.NativeWrapper.TevoLib.TevoLibWrapper,Common.NativeWrapper' to System.Type - Maybe type could not | 111360 |
| Alma 9 fails to boot after BMR due to incorrect naming in the fstab | 111359 |
| Failed connect to LiveDVD via ssh/sftp | 111358 |
| fix_boot.sh script does not work on new liveDVD. | 111357 |
| Agent service fails to start | 111356 |
| blk-snapshot kernel module failed to compile on 5.15.0-101.103.2.1.el9uek.x86_64 kernel. | 111309 |
| Alma, Rocky and CentOS do not detect / recognize LVMs except root after BMR | 111308 |
| Error in logs at stage "Fix boot request" is logged during BMR of EFI Alma, Rocky and CentOS | 111307 |
| Network is not available in restore console for LiveDVD | 111306 |
| There is no "Threshold" setting for Azure (NAS) repository | 111304 |
| Deploying Virtual Machine in Azure fails with "Error There is no sub net for network 'network name' " | 111303 |
| VM Option hangs on Loading in the Virtual Machine Export Wizard for Azure | 111298 |
| "Passphrase" field is absent in Protect Machine Wizard for Encryption Key step in Chrome | 111297 |
| Latest DKMS versions does not support REMAKE_INITRD flag | 111293 |
| Core service does not start | 111292 |
| Cannot add Backblaze B2 cloud account in URC | 111289 |
| Core doesn't obtain metadata from ESXi agentless VMs after upgrade from 6.7 to 6.8 (experimental build with vSphere 8) | 111286 |
| Mount of a recovery point is failing with "TevoMountReplay failed with error -2147023670 (0x800704ca - The network connection was gracefully closed)" in specific scenario | 111271 |
| Linked agents are showing duplicated on the LMU | 111262 |
| RHEL 8.x based machines reboots or hang during the transfer when data are being written to the disk | 111261 |
| Report email is not processing in the license portal for MSP Groups | 111260 |
| Failed to install NBD module on some kernels | 111259 |
| Core service fails to start with ComponentActivator: could not instantiate | 111258 |
| Cannot delete or detach Core from DL Appliances account | 111252 |
| The active license data displays incorrectly | 111251 |
| Incorrect QorePortal link in the Core's download tab | 111250 |
| Core/Agent install fails when recent vc_redist.x64/x32 2015-2022 are installed | 111248 |
This topic contains known issues in the following categories:
Table 3: Core and Windows known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 111365 | Core UI cannot be loaded if using SAML, it just tries loading in a loop | Core Console UI | |
| 111299 | Oracle integrity check fails | Oracle DB Support | |
| 111113 | SLES 12 SP5 fails to boot after BMR | ||
| 111095 | Export and BMR from Ubuntu 20.04 to VMware fails to boot. | ||
| 110991 | [ZD] Multiple Cores have the same ID | Metadata | |
| 110954 | [ZD] Restore is completed without any data restored (document is blank) and/or "Save as" is failing if DR, SQL and SP are installed on different servers | DocRetriever | |
| 110865 | Linux machine hangs from time to time while snapshot if some i/o data was generated for the same volume | None | Transfer, Linux, Core Service |
| 109771 | After canceling an ESXi export task when all volumes are in the post-processing phase, an error message appears. | Virtual export | |
| 109575 | On a specific environment, Core Console UI does not load, with the error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." | Core Console UI | |
| 109236 | Transfer job for VM with SharedVHDX on SOFS appears to fail with errors "Session with the id has not been found: fileTransmitSessionId" and "The process cannot access the file because it is being used by another process: " but recovery points actually are created. | ||
|
108972 |
Trying to perform an "Open Exchange Database" job from a recovery point fails with error "Multiple concurrent writable mounts of a single volume are not supported." |
Use the Local Mount Utility, or manually mount the recovery point and open the database. |
|
| 107978 | When deploying the Rapid Recovery Agent from the Core server, the Microsoft Store Install Service disappears from the list of services visible on the protected machine. | No workaround at this time. | Agent installation |
| 107947 | On a specific environment, virtual export fails to start, with error: 'Cannot connect to a remote machine '{0}' ' sometimes on unstable environment. | Contact Quest Support for a patch to resolve this issue. | Virtual export |
| 107855 | On a specific Dell PowerEdge Windows server environment, protected machine hangs briefly (up to 1 minute) every hour when the Rapid Recovery Agent service starts, seemingly due to a 20-30 BCD query. | Perform BCD queries one at a time, sequentially, to avoid this issue. For diagnostic steps, see Quest Knowledge Base article 259558. | Agent unresponsive |
| 107784 | When protecting a cluster, there is no ability to add cluster nodes to Virtual Standby | No workaround at this time. | Virtual export |
| 107755 | When creating an archive using the Archive Wizard, if you return from the Options wizard page back to the Machines page, there is no ability to edit the date range. | Close the wizard without saving the archive, and run through the wizard again. | Archiving, usability |
| 107346 | When restoring or performing virtual export of a volume with 512-bytes per sector to a volume with 4096-bytes per sector, a warning message does not appear. | For workaround, please see Quest Knowledge Base article 144232. | Virtual export, notifications |
| 107304 | On a specific appliance environment, the error message "GetResponse Timed Out" appears when trying to open the Appliance page. | Contact Quest Support for a patch to resolve this issue. | Appliance, Core Console UI |
| 107182 | Encryption key does not apply to cluster nodes during cluster protection. | Select encryption key for nodes manually in Settings. | Encryption |
| 106938 | On a specific appliance environment, the "Storage Hardware" information is not available on the Appliance Health page. | Contact Quest Support for a patch to resolve this issue. | Appliance, Core Console UI |
| 106545 | When upgrading a Core (in languages other than English) that protects machines with Agent version earlier than 5.4.3.106, the Compatibility page of the Rapid Recovery Core Installer wizard incorrectly shows Agent version 7 in the message instead of Agent 6.2 or Agent 6.3 (based on the installer being used). | None available. Disregard the version number. Protected machines with supported operating systems will be upgraded to Rapid Recovery Agent version 6.3. | Installer, localization |
| 105830 | Rollup job does not merge replicated recovery points according to the retention policy if seed drive for older recovery points was not consumed. | Consume the seed drive on the target core. | Rollup jobs, replication, seed drive |
| 105445 | Trustedinstaller process called during every metadata request from Agent, consuming about 100MB of additional RAM. | Contact for a patch to address this issue. | Metadata |
| 103477 | If the Quest NetVault Backup with BMR plugin is installed on the same server as the Rapid Recovery Core, then ESXi exports fail. | Copy the following DLLs from Coreservice\vddk\bin to the Coreservice folder, and then restart the Core service:
|
Virtual exports |
| 102390 | Drive letters are not assigned on an exported machine that is identical to the original machine. | Assign drive letters manually, or contact Support for a script to run on the exported machine that solves the issue. | Virtual exports |
| 97451 | Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM. | Assign drive letters manually. | BMR, ESXi agentless |
| 27309 93141 |
ESXi virtual export with automatic disk mapping using default configuration for the VM configuration location fails with unclear error. The Failure Reason is "Task 'ReconfigVM_Task' failed: Invalid configuration for device '0'." | Reduce the number of concurrent exports. | Virtual exports, ESXi |
Go to the top of the Known issues topic.
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 111206 | Linux volume metadata displays incorrectly. | Linux, Metadata | |
| 110865 | If I/O data is generated for a volume on a Linux machine, the Linux machine may not respond during a snapshot. | Linux, protected volumes | |
| 107984 | When installing Rapid Recovery Agent on a Linux machine, minor misspellings appear on the command line for firewall settings. | No workaround at this time. The text "Configured manualy. May be reconfigured…" is expected to be changed to "Configured manually. This may be reconfigured...". | Linux, Agent installation |
Table 5: Local Mount Utility known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 108540 | Toast pop-up notifications appear outside of the Local Mount Utility application window/frame. | No workaround at this time. | Notification |
| 107756 | Tthere is no ability to set Core Connection Timeout using the LMU UI. | You can set the Core Connection Timeout using the Windows registry using key CoreConnectionTimeout. For more information, see Quest Knowledge Base article 210006. | LMU, Connection timeout |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
