Solved

How to make Agent more tolerant of unstable network conditions?


Userlevel 2

I have a very unstable wireless connection on an endpoint that likes to go down during periods of high use, or just whenever it feels like it. Addressing the connection issue remains its own task, but for the time being, it seems like the Veeam Agent (Agent for Microsoft Windows 5.0.3.4708) is very intolerant to any sort of network issues. When the connection inevitably goes down, the backup process will be cancelled with the error:

Error: write: An existing connection was forcibly closed by the remote host Failed to backup file.

 

I’ve looked through the backup settings, and I did see one section titled Backup Cache which apparently is supposed to cache the backup locally until Veeam can connect to the server. Despite having this option enabled, the Agent still throws its hands up at the first sign of network trouble.

Hoping there is someone here who knows a magic trick to get the Agent to tolerate unstable connections, or can at least pass this along to the appropriate team.

Thanks!

icon

Best answer by Chris.Childerhose 13 February 2023, 19:16

View original

3 comments

Userlevel 7
Badge +20

Using the Backup Cache is the only method to circumvent this or possibly running during off hours where the network is less busy.  I would suggest posting in the Forums to put in any suggestions you might have but not sure how they can prevent unstable networking from being an issue to be honest.

https://forums.veeam.com/

Userlevel 2

Using the Backup Cache is the only method to circumvent this or possibly running during off hours where the network is less busy.  I would suggest posting in the Forums to put in any suggestions you might have but not sure how they can prevent unstable networking from being an issue to be honest.

https://forums.veeam.com/

Unfortunately, even the backup cache doesn’t seem to avoid this issue! Thank you for the link and response, I wasn’t aware there was another community.

Userlevel 7
Badge +20

Just to also mention. I had these same frustrations before and raised an R&D topic, I was suggested to use backup cache and advised the resume functionality in v5 would help. It didn’t! Perhaps you’d be willing to +1 on my feature request? They’ll likely want you to have raised your own support case to correlate findings: https://forums.veeam.com/veeam-agent-for-windows-f33/feature-request-modular-processing-of-veeam-agent-job-t76023.html

Comment