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 |
| 110899 |
On a specific environment, archive check failed with "Integrity check results: checksum errors, dedupe hash mismatches '0' have been detected." |
|
Archiving |
| 110887 |
In the Archive Wizard, the Folder Name field for cloud location is empty by default. |
|
|
| 110864 |
While attempting to restore a large volumne, BMR fails with timeout error or is unresponsive indefinitely. |
|
BMR |
| 110583 |
In one specific case, metadata recovery points appears appear inconsistent. |
|
|
| 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." |
No workaround at this time. |
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:
- glib-2.0
- gobject-2.0
- gvmomi
- iconv
- intl
- libcurl
- libxml2
- vixDiskLibVim
|
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 |
