An existing connection was forcibly closed by the remote hos

[Yanish]

Hi team,
Over he last few days I have been receiving this error during backups: "An existing connection was forcibly closed by the remote host"
On retry the job is successful.
I have Veeam on a physical server with a proxy. backups are stored locally on the Veeam Server.
I found the following KB regarding the issue - http://www.veeam.com/kb1781
Should the registry change recommended in the kb be performed on the Veeam server or the proxy server?

Thanks

[veremin]

Hi, Gil,

So, you're saying both backup repository and backup proxy server are deployed on one machine, right? I'm asking since this issue is typically related to packet loss between source and target backup component, and in case of all-in-one deployment network shouldn't be involved.

Thanks.

[foggy]

And since you have both Veeam B&R management server and proxy on the same machine, there should not be such a question where to deploy the mentioned registry key.

[foggy]

Joking apart, I believe the key should be deployed on the target server (the one receiving the connection), however it is not clear whether it is the proxy or repository component in your case, so I recommend providing logs for review to our support guys.

[Yanish]

Slight Correction.
I have a pyshical Veeam server whih is also my repostory.
I have a seperate virtual Proxy.
So I assume according to your answers that I need to make the registry change on the Repository?

[Vitaliy S.]

Since this error is talking about the remote host, then, yes, I believe you need to make these changes on the repository, but I will verify it tomorrow.

[veremin]

Anyway, as mentioned in the referenced KB article, the fist thing one having this issue should do is to check network connectivity between backup components and see whether it's stable or not, as this is the most frequent cause of this error. So, have you already checked it? Thanks.

[Yanish]

Yes, as far as we can tell there are no network issues.
We also changed time of backups incase something was interfering.
Also, retries always succeed.
We will attempt the registry key change and cotact support of that does not help.

Thanks

[veremin]

The best idea, indeed, as we can spend weeks guessing via the forum correspondence. Meanwhile, the support team should understand the root cause after analyzing corresponding logs and infrastructure.

Anyway, keep us updated how this process goes.

Thanks.

[Shralok]

I am having this same error and Veeam is backing up the specific server over a site-to-site VPN. Would a WAN accelerator help in this situation?

Veeam Host & Backup Repository - Server 1
Remote Server - Server 2

Server 1 reaches over a site-to-site VPN to back up Server 2 which is a VM on a Hyper-V 2008 R2 host (this host is also the proxy).

Thank you

[foggy]

WAN acceleration is used in the backup copy jobs, not regular backup jobs. You need to backup the VM locally first, then use Backup Copy job to transfer backups to the remote site with WAN acceleration.

[rickyelqasem]

I get the same problem while restoring a backup. It was suggested it could be network problems but I don't believe it so. This is what I tried. Restoring to different hosts = failed. Restoring over a isolated vswitch with no pNIC to prove its not my network = failed.

Anyone got a fix for this yet?

[foggy]

What if you copy the backup to some other location, import it and try to restore from there? I would also contact support with this.

[albertwt]

So what was the root cause of this issue ?

Error: Socket has been forcibly closed. Failed to recover connection.

[foggy]

There could be several reasons, if you see this in your environment, the best step would be to contact support.

[tranquilon]

I was going crazy with this issue until I found the culprit. I added a second IP to the proxy connection in order to access a subnet. I didn't delete it but didn't remember I added it either. Guess what? I deleted the address and backups are running like a charm again.

[iyoung]

Hi,

Thanks for the post tranquilon, exactly my problem. You've saved me lots of hassle.

Cheers

Ian