-
Title
Unable to mount the recovery point using LMU fails with timeout error -
Description
Mounting the recovery point using Local Mount Utility (LMU) and it fails to mount and throws an error "Core service cannot be reached. Please check the network connection and if the service is running." -
Cause
This is because of the LMU connection timeout with Core server, when mounting the recovery point of bigger sized data. -
Resolution
Open the Core UI and navigate to the settings page. Confirm the Replay Engine IP is set correctly.
1. Open the LMU installed on Agent machine with Administrator rights.
- Open Local Mount Utility
- Click on Options.
- Increase the Core Connection Timeout (min) to 30 Mins (default is 5 min).
- Click OK and try mount the recovery point.
If still facing the same problem, follow step #2.
2. Check if the replay engine IP address is correct, if not then change it to the correct.
NOTE: do not use IPV6. Change to the IPV4 address if needed.
If still facing the same problem, follow step #3.
3. Set the filter driver timeouts on AAVdis and AAVStor to 12000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AAVdisk\Parameters
AsyncNetworkTimeout=12000
NetworkTimeout=12000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AAVStor\Parameters
NetworkTimeout=12000
If LMU is on the core then restart the core service.
If still facing the same problem, open a SR from Quest portal in order to be reviewed by our Support team.
-
Additional Information
Also you should able to see "The semaphore timeout period has expired" on AppRecovery.log