connection try has failed

Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)

connection try has failed

Veeam Logoby omfk » Sat Jul 15, 2017 9:56 pm

Hello,

since some days I notices that my VAW needs several retries before it finishes its job. The error is always
Code: Select all
15.07.2017 23:48:41 :: Error: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.


A connection try has failed, as the other side hasn't responded after a certain time span or the established connection was faulty, as the connected host didn't reacted.

A ping from source to Veeam server works and I can also "see" the repository when entering the configuration dialog.

What can I further to check to nail down the specific cause?

The connection runs over a WAN-VPN-connection.

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Shestakov » Sun Jul 16, 2017 9:06 pm

Hello Frank,
it`s hard to say since the error message is in German. Could you provide the support case number?
Thanks!
Shestakov
Veeam Software
 
Posts: 5034
Liked: 419 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: connection try has failed

Veeam Logoby Technogod » Sun Jul 16, 2017 10:48 pm

Examine log file of specific job that is failing. Logs are located in C:\ProgramData\Veeam\Backup
Technogod
Enthusiast
 
Posts: 79
Liked: 13 times
Joined: Tue Apr 11, 2017 3:52 am

Re: connection try has failed

Veeam Logoby omfk » Mon Jul 17, 2017 7:57 am

This error is related to the following case: 02223477
In this specific case the error appeared not in the beginning but in the merging phase.

Some lines around the error from the log file:
Code: Select all
[16.07.2017 23:30:08] <10> Info             [RemoteBackupService] Remote session has been started, id: '75e606a8-14c3-4483-bef6-cdc3aed563f5'
[16.07.2017 23:30:09] <10> Info     Local protocol version: 5, remote protocol version: 5
[16.07.2017 23:30:09] <10> Info     Protocol version check returned - Compatible
[16.07.2017 23:30:09] <10> Info     [RemoteBackupService] Creating LeaseKeeper for session [75e606a8-14c3-4483-bef6-cdc3aed563f5] and lease [79eb9d55-a86f-4303-90c4-485ca11db061]
[16.07.2017 23:30:09] <10> Info     [LeaseKeeper] Created, ttl 1800sec
[16.07.2017 23:30:31] <18> Info     Networking error: [Ein Aufrufziel hat einen Ausnahmefehler verursacht.. Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat]
[16.07.2017 23:32:31] <18> Info     [RemoteBackupService] Terminating remote session, id: '5dafe576-35f7-4aa6-a7b3-6db104699bc8'
[16.07.2017 23:32:34] <18> Info     [RemoteBackupService] Remote session was successfully terminated.
[16.07.2017 23:32:34] <18> Error    Failed to notify remote VBR server that endpoint job has been updated
[16.07.2017 23:32:34] <18> Error    Connection problems. (Veeam.Backup.Common.CustomStackException)
[16.07.2017 23:32:34] <18> Error    Veeam.Backup.Common.CMethodRetryException:
[16.07.2017 23:32:34] <18> Error       bei Veeam.Common.Remoting.CRetryableMethod.DoInvoke(Delegate dlg, Object[] args)
[16.07.2017 23:32:34] <18> Error       bei Veeam.Common.Remoting.CRetryableMethod.Invoke[Ret](ActionDelegate`1 dlg)
[16.07.2017 23:32:34] <18> Error       bei Veeam.Backup.Core.CForeignInvokerClient.InvokeInternal(CForeignInvokerParams invokerParams)
[16.07.2017 23:32:34] <18> Error    Ein Aufrufziel hat einen Ausnahmefehler verursacht. (Veeam.Backup.Common.CustomStackException)
[16.07.2017 23:32:34] <18> Error    System.Reflection.TargetInvocationException:
[16.07.2017 23:32:34] <18> Error       bei System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
[16.07.2017 23:32:34] <18> Error       bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
[16.07.2017 23:32:34] <18> Error       bei System.Delegate.DynamicInvokeImpl(Object[] args)
[16.07.2017 23:32:34] <18> Error       bei Veeam.Common.Remoting.CRetryableMethod.DoInvoke(Delegate dlg, Object[] args)
[16.07.2017 23:32:34] <18> Error    Von der Übertragungsverbindung können keine Daten gelesen werden: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. (Veeam.Backup.Common.CustomStackException)
[16.07.2017 23:32:34] <18> Error    System.IO.IOException:
[16.07.2017 23:32:34] <18> Error       bei Veeam.Backup.Core.CForeignInvokerClient.Wait(WaitHandle waitObj, State state, Int32 timeout, String timeoutError)
[16.07.2017 23:32:34] <18> Error       bei Veeam.Backup.Core.CForeignInvokerClient.<>c__DisplayClass2.<InvokeInternal>b__0()
[16.07.2017 23:32:34] <18> Error    Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat (Veeam.Backup.Common.CustomStackException)
[16.07.2017 23:32:34] <18> Error    System.Net.Sockets.SocketException:
[16.07.2017 23:32:34] <18> Error       bei System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)


BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Mon Jul 17, 2017 4:22 pm

Hi Frank,

Thanks for sharing case ID. Try to start a file level recovery from any backup file residing Veeam repository and share the result.
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: connection try has failed

Veeam Logoby omfk » Tue Jul 18, 2017 8:21 am 1 person likes this post

I've tried to restore a single file from the full backup and it was successful. Right now the incremental backups are running fine and also the "Full backup file merge completed successfully".

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Tue Jul 18, 2017 12:39 pm

Glad to hear you are up and running. Keep us posted if you face this issue again. Cheers!
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: connection try has failed

Veeam Logoby omfk » Thu Jul 20, 2017 4:32 pm

Dima P. wrote:Glad to hear you are up and running. Keep us posted if you face this issue again. Cheers!


Well, it's not really over.

Yes, I can restore from the backup in question. The failed connection issue, however, is still there. As long as the failures only occur before making the backup itself, it only postpones the backup.

Current suggestion from support is "interference" with AV activities. So far it is not clear if we are talking about the server to be backed up or the VBR server. If this is really an issue then the question remains, why this hasn't happened earlier.

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Thu Jul 20, 2017 5:36 pm

Frank,

Sorry, I thought it was a temporary glitch. If the issue is sporadic - routing, indeed, sounds like good thing to check. Try to add VAW to your AV exclusions, make sure that you have all ports opened between VBR repository and agent. I’d also check the firewall on router: for testing purposes you can disable it and make a couple of test job runs to check the results.
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: connection try has failed

Veeam Logoby omfk » Wed Jul 26, 2017 8:09 pm

According to the suggestions and the KB article I excluded certain Veeam directories of the VAW and VBR machine from the AV scanning regime. It worked for some days but just some minutes ago the error happened again:
Code: Select all
26.07.2017 21:48:26 :: Error: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat


What I really find strange is the fact that this messages comes in German, whereas all the rest of the content inside the information window is in English.

When I look up the error message on google I get mostly hits on database issues. Is there an option to get more debug information from VAW?

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Wed Jul 26, 2017 10:47 pm

Any chance this error could be generated by VBR running in German locale?
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: connection try has failed

Veeam Logoby omfk » Thu Jul 27, 2017 1:33 pm

When I start the VBR console either on my PC or on the VBR server itself, all content is in English. The language of the OS, however, is German.

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Thu Jul 27, 2017 6:07 pm

Frank,

Understood. Then this error might be generated as a response from Veeam B&R server. Do you still have the original case opened (I think the root cause is somewhere in VAW and VBR debug logs)?
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: connection try has failed

Veeam Logoby omfk » Fri Jul 28, 2017 8:35 am

The case is still open. Unfortunately I'm on vacation the next two weeks.

BR
Frank
omfk
Enthusiast
 
Posts: 54
Liked: 6 times
Joined: Wed Nov 30, 2016 9:48 pm
Full Name: Frank Knappe

Re: connection try has failed

Veeam Logoby Dima P. » Fri Jul 28, 2017 2:21 pm

Thanks for the clarification. I believe you can ask support folks to keep the case opened for a while and get back to us later. Have a good vacation! :wink:
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov


Return to Veeam Agent for Windows



Who is online

Users browsing this forum: No registered users and 15 guests