Return
-
Title
Transfer fails with network timeout error at "determining data" step on a snapshot. -
Description
Backup of a specific agent fails with the following error or similar:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
On the agent, the ApprecoveryPM.log file show the following events before the jobs fails:
INFO 2021-09-21T10:45:31 [12] - Replay.Agent.Implementation.Transfer.TransferDataServer (RequestUri=https://AgentName:8006/apprecovery/api/agent/transfer/snapshots ClientAddress=IP:57224 Service=Replay.Agent.Management.Transfer.TransferManagement Method=TakeSnapshot)Listening on tcp://0.0.0.0:8009/INFO 2021-09-21T10:55:31 [70] - Replay.Agent.Implementation.Transfer.TransferSessionBase ()Transfer 38bba298-c9dd-4e9b-8ffb-ac6c72bcfe0d initiated 9/21/2021 3:45:31 PM has been idle for 00:10:00.0130936, which is beyond the specified transfer timeout of 00:10:00; this transfer will be abandoned -
Cause
One possible cause for this error is that port 8009 may be in use by another application on the Agent server itself and/or blocked by a firewall.To test this, run the following command from an elevated command prompt on the agent:>> netstat -ano | find "8009"The output from this will tell you which application is listening on, or has an established connection on port 8009. -
Resolution
If port 8009 is not in use by another application on the agent, you may have to check on firewall internal/external settings to unblock port.If the output shows an application other than Rapid Recovery using this port then go to the Core console and select the Agent, then go to "Setting > Transfer Settings" and change the "Transfer Data Server Port" setting to an available port, then test snapshot. Ensure that the new port is actually free on the agent by running the same command as above and replacing with the new port number.You may need to reference the Rapid Recovery firewall requirements settings KB to ensure the ports at play: