WAN Replication failing

[dellock6]

Anton is spot on. Veeam added more resilience to network problems in 6.1 patch 1, and your issue sounds like those solved by the patch.

Luca.

[wisecra]

Backups of my largest VMs go to 100%, then when removing snapshot, get a
|Error: Client error: An existing connection was forcibly closed by the remote host Failed to process [sendSignature]. |
error and fail.

Don't think it's connectivity - Jobs on larger VMs progress to 100%, then fail when removing snapshots.

Smaller VMs seem to run fine. Has anyone seen anything like this?

Veeam Support Case # 00165337
Environment:
+ Veeam 6.1.0.215 (64bit)
+ Replicating from one ESXi 5.0 host to one at a remote datacenter
+ WAN, 3mb limit set for business hours, and an 8mb limit set for afterhours.
+ Veaam backup server is at remote site, proxy servers are located at both sites.

[veremin]

Has anyone seen anything like this?

For me, it sounds like patch 1 for VB&R 6.1 should be the solution for you issue. This patch can be obtained from technical support team.

Furthermore, in order to find useful information regarding your problem, it might be worth looking at the posts above.

Thanks.

[wisecra]

For me, it sounds like patch 1 for VB&R 6.1 should be the solution for you issue.

Thanks for the reply - I have read this thread repeatedly and already applied Patch 1 - that's why I'm now getting to 100% (I had to play with the MTUs to get this far).

[capitangiaco]

HI all

I have a similar problem on my radio link.
I am using a remote repository throught a 20megabit/s radio link (with ipsec).
For about 4 months I had no problems, I reached the 89 restore points.
Two weeks ago backups begin to fail every days (I have two jobs, one for windows vms and the other one for linux vms).
I created new jobs towards that repository and I noticed that now some vms are backed up and others no with the error: An existing connection was forcibly close by host...
After used new jobs, the old ones now start and backup randomly some vms.
I feel that it's like veeam thinks that backup is still running, or the vm is in use in other jobs (but all jobs are stopped)
Instead I have no problems in with the other two repository (in LAN/MAN)

(I am using Veeam Backup and Replication 6.1.0.181, the remote repository is a windows 2003 server sp2)

Giacomo

[capitangiaco]

Active Full backups (of the failed jobs) works without problems.

Giacomo

[Vitaliy S.]

Hi Giacomo,

I created new jobs towards that repository and I noticed that now some vms are backed up and others no with the error: An existing connection was forcibly close by host...

I feel that it's like veeam thinks that backup is still running, or the vm is in use in other jobs (but all jobs are stopped)

Well...given that you have these failures on random VMs, I still think that it might be related to connectivity issues. Anyway, what does our support team say you after reviewing your debug log files?

Thanks!

[capitangiaco]

Hi Giacomo,

Well...given that you have these failures on random VMs, I still think that it might be related to connectivity issues. Anyway, what does our support team say you after reviewing your debug log files?

Thanks!

Hi

support is asking me job.Target.log file that I don't have...
The really question is: why full active works perfectly and incremental (reversed) fails ?

Giacomo

[Vitaliy S.]

The really question is: why full active works perfectly and incremental (reversed) fails ?

It's almost impossible to answer that question without looking into the log files. Let your support engineer that you do not have this file and continue working on this issue.