Export hangs at 95% and the Core's UI is unresponsive if WriteCachingPolicy is ON in Windows 10 22H2 (4375063)

Export hangs at 95% and the Core's UI is unresponsive if WriteCachingPolicy is ON in Windows 10 22H2

When the WriteCachingPolicy is set to "On" on Rapid Recovery Cores installed in Windows 10 22h2 environments, an issue occurs causing the Rapid Recovery service to crash during exports. This issue is not observed on Windows 10 21h2 or Windows 11 platforms and specifically arises during export operations.

Steps to Reproduce:

1. Install Rapid Recovery Core on Windows 10 22H2.
2. Create a DVM repository and Set the WriteCachingPolicy to "On" in Advanced options.
3. Protect an agent by installing the agent or agentless.
4. Force a snapshot.
5. Perform an export operation.

Expected Result:

The export operation completes successfully without any errors. The Core UI remains responsive.

Actual Result:
During the export operation, the export hangs at 95%, and the Core UI becomes unresponsive. Eventually, the export fails after an extended period.

Errors Encountered:

• Replay.Core.Contracts.Export.ExportException: One or more dependent export tasks have failed. --> System.ComponentModel.Win32Exception: TevoInstallVmScsiDriver failed.
• Replay.Core.Contracts.Export.ExportException: One or more dependent export tasks have failed. ---> System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> Replay.Common.Contracts.Win32Api.Win32ApiFailedException: Failed to open '?\Volume{UUID}' - The system cannot find the file specified.
• Replay.Common.Contracts.Win32Api.Win32ApiFailedException: Failed to open '?\Volume{UUID}' - The system cannot find the file specified.

The issue has been identified as defect RR-111444. The defect will be evaluated by our Product Team for inclusion in a future release of Rapid Recovery. 

A list of "Resolved Issues" is published in the product Release Notes accompanying new releases that can be referenced to identify if a fix for this defect has been implemented. Product Release Notes are available in the "Release Notes and Guides” area of our Support Portal at Rapid Recovery Technical Documents. 

For more information on our Product Enhancements and Defects policy, see details published in our Global Support Guide available on the Support Portal.

1. Ensure that when creating a new repository or adding an extent, the default write caching policy (OFF) is used.
   • When adding extents, ensure consistency by using the same write caching policy for all extents.
2. Change the write caching policy to the default value (OFF).
   • Refer to the following knowledge article for detailed instructions: High Paged Pool RAM Utilization on Systems Running Rapid Recovery (4035226) (quest.com).

 

If the issue persists after following the above steps, please don't hesitate to contact our support team at Create Technical Case (quest.com) for further assistance. Our dedicated support staff will be happy to help resolve any remaining issues or provide additional guidance as needed.

RR-111444