Problem with vmdk restore

[Benjamin Ritter]

Hello,

i have a problem with restoring a vmdk to the filesystem.

Every time i get the error:

Error: bsock_tcp.c:407 Write error sending 65536 bytes to client:192.168.199.9:9103: ERR=Die Verbindung wurde vom Kommunikationspartner zurückgesetzt

Fatal error: read.c:156 Error sending to File daemon. ERR=Die Verbindung wurde vom Kommunikationspartner zurückgesetzt

If i want to restore a other vm it works like e charm with the same plugin settings

I run version 17.2.6-21.1 as Director and sd on a UCS

The fd runs on debian with version 17.2.4-9.1

How can i fix this ?

best regards

Benjamin Ritter

[Andreas Rogge]

Hi Benjamin,

Am 14.03.19 um 08:06 schrieb Benjamin Ritter:

> Error: bsock_tcp.c:407 Write error sending 65536 bytes to

> client:192.168.199.9:9103 <http://192.168.199.9:9103>: ERR=Die

> Verbindung wurde vom Kommunikationspartner zurückgesetzt

> Fatal error: read.c:156 Error sending to File daemon. ERR=Die Verbindung
> wurde vom Kommunikationspartner zurückgesetzt

(the error message means "Connection reset by peer")

This error indicates that the connection has been closed by "the other
end". This usually happens when a firewall between the components
(Director/FD, FD/SD, Director/SD) times out one of the control channels
even when keepalive is set.
You can usually work around this by configuring "Heartbeat Interval" in
the right places (take a look at the docs).
If you need to know what connections are used, take a look at
https://docs.bareos.org/bareos-18.2.html

> If i want to restore a other vm it works like e charm with the same
> plugin settings

Is the other VM smaller so you don't run into the firewall timeout?

> I run version 17.2.6-21.1 as Director and sd on a UCS
> The fd runs on debian with version 17.2.4-9.1

While this should work the official requirement is that Director and SD
version must match.

Best Regards,
Andreas

--
Andreas Rogge andrea...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz

[blabl...@gmail.com]

Hi, yes the working vmdk is way smaller 20gb, the problematic one has 1,5tb

i will check that with the firewall

thank you

[blabl...@gmail.com]

Heartbeat and timeout settings didnt work,

i see on the fd the keepalive packets, but the same connection refused error appears.

The sd and dir on the same vm, fd with vadp-dumper on other vm on the same esx, vcenter also on the same esx


I have no glue how to restore the vm

Maybe its related to the different Versions, but sd and dir are univention, fd is debian8 because off the vmware packets not available on univention.

Am Donnerstag, 14. März 2019 08:06:49 UTC+1 schrieb Benjamin Ritter:

[blabl...@gmail.com]

Maybe i found the error, but i how i can fix it ?


python-fd.c:1183-33620 python-fd: Traceback (most recent call last):
File "/usr/lib/bareos/plugins/BareosFdWrapper.py", line 66, in create_file
return bareos_fd_plugin_object.create_file(context, restorepkt)
File "/usr/lib/bareos/plugins/BareosFdPluginVMware.py", line 296, in create_file
cbt_data = self.vadp.restore_objects_by_objectname[objectname]['data']
KeyError:

Am Donnerstag, 14. März 2019 08:06:49 UTC+1 schrieb Benjamin Ritter:

[Ciroc]

I was wondering if you were able to find the root cause of this issue?
I am getting the same error both on the 22 and 21 versions.