-
标题
Repository Mount Stuck at 80% After Upgrading Rapid Recovery -
说明
After upgrading to a newer version of Rapid Recovery the "Maintaining DVM Repository" job seems to be hung at 80%. The progress bar shows no movement for hours. The subtask "Checking volume images by read" shows no percentage number.
-
原因
In some environments, after upgrading Rapid Recovery the core determines that an integrity check needs to be executed on the repository. Additionally, this job is nowhere to be seen running, resulting in the mount job appearing to be stuck when looking at it on the core console. -
解决办法
Allow the repository mount job to complete its cycle. Factors that affect how long it will take to finish include repository size, volume I/O, available RAM, and/or CPU power/type.To confirm that the core is actually working on mounting the repository, you may do this:
- On the core, browse to the directory "C:\ProgramData\AppRecovery\Logs"
- Look at the "Date modified" time-stamp for the "AppRecovery.log" file. It should be very close to the current time.
- Open the "AppRecovery.log" file with Notepad and scroll to the bottom of the log to see the most recent events.
- Search for an event similar to the following:
DEBUG 2018-01-02T19:37:18 [839] - Replay.Core.Implementation.RecoveryPoints.Checks.VolumeImageChecker (Job Id = a0df20b2-6372-cff5-c0a5-decf8a248169:MaintainRepositoryJob cd53cf4b-7702-0191-cdf9-e4654fed0855:RepositoryVolumesReadCheckJob) Executing StartReadMetadata for volume image 'Incremental of 'C:\' on 'protected_machine_name' as of '8/31/2017 6:49:16 AM' (1/1/1901 12:00:00 AM local time)'
Or
DEBUG 2018-01-02T19:37:18 [839] - Replay.Core.Implementation.RecoveryPoints.Checks.VolumeImageChecker (Job Id = a0df20b2-6372-cff5-c0a5-decf8a248169:MaintainRepositoryJob cd53cf4b-7702-0191-cdf9-e4654fed0855:RepositoryVolumesReadCheckJob)
Starting to read metadata for volume image 'Incremental of C:\' on 'protected_machine_name' as of '8/31/2017 6:49:16 AM' (1/1/1901 12:00:00 AM local time)'
If you do see these it means the job is indeed running, so just allow the core to finish this integrity check and all tasks will resume once done. This is a one-time thing, the core should not do this lengthy mount job again later on.