The following is a list of enhancements implemented in Rapid Recovery 6.9.
Table 1: General enhancements
| Enhancement |
|---|
|
|
The following is a list of enhancements implemented in Rapid Recovery 6.9.
Table 1: General enhancements
| Enhancement |
|---|
|
|
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.9:
The following applications are no longer support by Rapid Recovery as of release 6.9:
The following Intel Core processor families are no longer supported by Rapid Recovery Core installation or upgrade starting with 6.9 release:
The following table includes a list of issues addressed in this release.
Table 2: Issues resolved in this release
| Issue Description | Issue ID |
|---|---|
| Upgrade MongoDB migration step failed with the status message: 'Warning: System.IO.DirectoryNotFoundException'. | 111558 |
| Core upgrade to 6.9 finishes with MongoDB upgrade warning. | 111550 |
| Replace 'enabled legal hold' to 'Legal hold' if object-locking is enabled. | 111513 |
| Archive fails with error "Object reference not set to an instance of an object" after turning off object-locking setting. | 111512 |
| Archive fails with "Invalid Object Locking setting!" when enabled legal hold and disabled retention mode. | 111511 |
| Governance Retention mode is available on Compliance bucket after editing existing archive. | 111510 |
| Settings to turned off the object-locking setting for an existing archives tab is unavailable. | 111508 |
| While unmounting repository a warning is displayed "All active tasks of this Repository will be cancelled. Do you wish to proceed with the check of Repository?". User need to accept if they wishes to continue. | 111486 |
| Archive to Backblaze fails with "Access Denied" if Bucket-Level Object Retention is enabled. | 111484 |
| Retention mode: Governance is not available in UI for Backblaze. | 111483 |
| Archive to Backblaze fails with "Missing required header for this request: Content-MD5" if Bucket-Level Object Retention is enabled. | 111458 |
| Archive to Wasabi fails with "Object locking is not supported by selected container!" if Bucket-Level Object Retention is enabled. | 111457 |
| Service endpoint is missing for Amazon S3 in URC. | 111455 |
| Archive to QoreStor S3 fails by time out error. | 111453 |
| Archive to S3 fails with Exception. The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. | 111451 |
| Cannot add S3 to cloud account type. | 111450 |
| The retention period is reduced by 1 day after each opening window in the Object Lock. | 111448 |
| Archive job failed every time after 15 minutes of normal running. | 111447 |
| Archive to QoreStor S3, B2, Wasabi fails by time out error. | 111440 |
| Export for Volume(s) with file system 'ReFs' on Windows 11 fails with TevoGetFlagsInOfflineVolume failed with error -2147024893 (0x80070003 - The system cannot find the path specified). | 111435 |
| Uninstall of Core does not remove fips.config file. | 111434 |
| 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 |
| Cannot install Core on Windows Server 2019. | 111425 |
| Cannot install RR Core due to "This publisher has been blocked" error. | 111424 |
| Upgrade Mongo fails with "Operation is not valid due to the current state of the object" error. | 111422 |
| 'Unmounted' should be aligned in the section and fully displayed. | 111420 |
| Core installation fails with "Cannot find object or property" error on the Windows server 2016. | 111418 |
| Installer hangs on Installing Drivers stage if FIPS is enabled. | 111417 |
| Core installer fails with "The system cannot find the file specified" error. | 111416 |
| Cannot add QoreStor S3 cloud account in URC. | 111414 |
| Core service fails to start due to error "ComponentActivator: could not instantiate Replay.Core.Implementation.Events.EventsStorageService" | 111413 |
| Replication server incorrectly shows linked VMs (ESXi/Hyper-V) under hypervisor on Home UI view. | 111385 |
This topic contains known issues in the following categories:
Table 3: Core and Windows known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 111617 | MongoDB service fails to start after Rapid Recovery core upgrade on hardware which does not meet MongoDB system requirements (KB 4041708) | ||
| 111517 | Error: "While Compliance mode is working; you cannot change the mode and retention period cannot be shortened!" | ||
| 111487 | When adding a Linux VM to agentless protection (VMware), the error occurs: "The partition size is incorrect, please shrink the volume." | ||
| 111449 | Transfer fails with GetResponse Timeout error after resizing an LVM volume. | ||
| 111444 | Export hangs and the Core's UI is unresponsive if WriteCachingPolicy is ON | ||
| 111439 | No ability to create repository with size more than 250 TB independently of FS allocation unit size | ||
| 111432 | Core service is crashing in specific environment during restore from a cloud archive (Wasabi) | ||
| 111387 | Core service crash with error "Not enough memory" and / or memory leak on specific environment | ||
| 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 | |
| 111206 | Linux volume metadata is showing incorrectly. | ||
| 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 |
| 107756 | There is no ability to set Core Connection Timeout in UI | ||
| 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 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center