WORKAROUND1:
Installing Service Pack 1 on the Exchange deployment may resolve the mountability error
WORKAROUND 2:
This issue should be fixed by increasing of the driver timeouts:
1) Extend the AAVDisk NetworkTimeout , AsyncNetworkTimeout and and AAVStor NetworkTimeout driver to 600 000 (dec).
- Suspend all transfers.
- Allow current Exchange mountability checks to complete.
- Ensure all mounts have been dismounted.
- Shut down Core service.
- Stop the AAVDisk and AAVStor drivers. (use next commands in cmd: 'sc stop aavdisk', 'sc stop aavstor')
- Extend the AAVDisk and AAVStor driver NetworkTimeout to 600 000 (dec) (1 minute). The values are located at HKLM\SYSTEM\CurrentControlSet\Services\AAVdisk\Parameters\ and HKLM\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters\
- Open registry editor and navigate to HKLM\System\CurrentControlSet\Services\AAVdisk\Parameters\AsyncNetworkTimeout
Create the key AsyncNetworkTimeout REG_DWORD and set the value to 600000.
- Start the AAVDisk and AAVStor drivers. (sc start aavdisk, sc start aavstor)
- If the drivers will start, then start Core service and resume transfers.
- If the drivers won't start, then reboot the core server.
- After the reboot, start the Core service and resume transfers.
2) Increase Replay Engine Configuration, Replay Engine Read and Write Timeout to 15 minutes
if that does not help please do the following:
1. Remove agent from protection keeping RP
2. Reboot Core server
3. Reboot Agent server
4. Add the machine to protection