Veeam 7 patch 3a messes up veeam

[itpfp]

Right, updated veeam 7 to pach 3a. And I am getting precisely the error that the document claims has been fixed, even though prior I never had this problem:

•Job may fail VM processing if backup proxy has a very large amount of NICs with the “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond” error. To work around this, increase the timeout by creating the newly introduced ConnectByIPsTimeoutSec (DWORD) registry value.

No further documentation on the mentioned registry value either.

Can someone please tell me what the hell is going on here ?

[foggy]

Have you tried to apply this registry key (it should be placed under Veeam B&R standard HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication hive, the default value is 300)? If this doesn't help, please contact technical support directly.

[itpfp]

I just did, same thing (I restarted veem services). It times out after 22 seconds after preparing next vm for proccessing.

Or should I apply this key on the hyper-v boxes themselves ? To bad there doesn't seem to be any documentation about this (I did try and search for it).

edit: error message:

Code: Select all

17-3-2014 18:06:46 :: Processing 'SVE-DC001' Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.56:2500

I tried several vm's on different hyper-v hosts, none of them get past this stage.

[veremin]

Or should I apply this key on the hyper-v boxes themselves ? To bad there doesn't seem to be any documentation about this (I did try and search for it).

No, it should be applied on backup management server. All exiting registry keys go to standard HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication hive. Thus, we don't keep reiterating it.

I would recommend opening a ticket with our support team and let them investigate this behaviour directly.

Thanks.

[Gostev]

It is extremely unlikely that your issue is connected to the upgrade anyhow.

[RomanAxBe]

I have the same failure

Code: Select all

02.07.2014 13:29:30 :: Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.10.64:2500

what can I do? the regisitry key is created...

The Veeam Version:

[Vitaliy S.]

If it doesn't help, then please contact our technical team for further investigation of the issue. Thanks!