Return
-
Title
Semaphore timeout occurs after 5 (five) minutes during Rollback Operation -
Description
When attempting a rollback of a large volume, a semaphore timeout occurrs and the rollback fails at 5 minutes. Attempts to edit the AAVDISK parameters on the core have been tried and are unsuccessful. -
Cause
The problem lies with the AAVDISK parameters on the target machine where the restore needs to occur on. -
Resolution
Complete the following steps.
- Confirm that the Core and BMR/Export target are connected through a 1Gbps network with no 10/100Mb devices between them.
- Disable any unused NICs on the Core in the Device Manager.
- In the Core Console, navigate to the Configuration tab and select Settings.
- Select Replay Engine Configuration.
- Increase the Read and Write Timeouts to 15:00 (15 minutes).
- Restart the Core Service.
If you experience a semaphore time after progressing X% into the rollback, complete the following steps.- Reboot the URC Console and Core machines.
- Once the Core is operational, pause all snapshots, exports, and replication activity and initiate the rollback again.
- In this instance, the semaphore even occurs because there is high repository activity during the rollback, cause the semaphore to timeout.
Another step would be to increase the driver timeouts on the
- On the target agent machine, In Regedit, edit the following registry values:
- HKLM\System\CurrentControlSet\Services\AAVDISK\Parameters\AsyncNetworkTimeout: set to 1800
- HKLM\System\CurrentControlSet\Services\AAVDISK\Parameters\NetworkTimeout: set to 1800
- In a command window, type "SC STOP AAVDISK, " then "SC START AAVDISK"
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.