Current job logic gathers metadata for each database before the Mountability or Checksum Check job runs for that individual database. In the image below, the actual Mountability check takes minutes at most. However, there are gaps in between the jobs up to 30 minutes or longer. These gaps are when the Core is gathering metadata for the next database.
On Exchange servers with large numbers of databases, this can cause these jobs to take hours to complete. While Mountability and Checksum Checks are running, Core performance for other jobs such as transfers, replication, and exports, can be greatly reduced.
This issue has been identified as Defect RR-101797.
Development has developed a patch that changes the metadata gathering logic for Mountability and Checksum Check jobs. The patch will improve performance of these jobs by gathering all the metadata at the beginning of the job, instead of gathering for individual databases as the job runs. This eliminates the large gaps of time in between individual database checks.
In a test environment with an Exchange server with a 2.5 TB database volume containing 27 databases, Mountability Check times were reduced from an average of 5 hours to under 30 minutes after the solution was applied.
Please contact Support to request a patch for your Rapid Recovery Core. The patch is build specific and will need to have a new patch applied after upgrades until the logic changes are added to a future build for a permanent solution.
Note: Development will insist that the patch be created for only the the most recent build of Rapid Recovery. Please upgrade before submitting a CR if possible.
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Patch also add functionality to change the default mount point path. By default the path is C:\ProgramData\AppRecovery\MountPoints. If you see to much disk activity and / or disk queue on C: during Core jobs that mount recovery points, you can change the default path to another volume that is not C: or the Repository volume: