- Veeam Support Knowledge Base
- Connection forcibly closed by remote host
Connection Forcibly Closed by Remote Host
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
While a job is processing, a job may intermittently fail while sending data from the source proxy to the target proxy/repository server with:
srv| ERR |Server session thread has failed. srv| >> |An existing connection was forcibly closed by the remote host
Cause
Solution
Some common tools typically recommended for testing are Iperf as it can give quite a bit of information about the network connection and Wireshark.
More Information
If the "forcibly closed by the remote host" error occurs consistently, a full investigation of the network instability is suggested as documented in the Solution section above. However, if the error only occurs occasionally, it is possible to adjust the number of reconnect attempts the agent processes perform. To do so, create the following registry value on the Veeam Backup server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: AgentMaxReconnectRetries
Value Type: DWORD (32-bit) Value
Value Data (Default): 30
The default is 30 retries. This may be increased as needed.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
