Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.
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.
This issue is resolved starting with Rapid Recovery 6.1.2. Please upgrade to the latest version of Rapid Recovery.
Development has changed the metadata gathering logic for Mountability and Checksum Check jobs. Changes 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.