Re: [Bacula-users] Restore to Windows client fails if file is too big

2018-02-19 Thread Kenneth Garges
Thanks to everyone that responded. I’ve solved the problem. We had 4 10Gbs network interfaces aggregated together using LACP. Running some tests trying to send data to a Windows client we found the problem is not just Bacula. Even ftp failed if the file size was bigger than about 1300 bytes.

Re: [Bacula-users] Restore to Windows client fails if file is too big

2018-02-19 Thread Tilman Schmidt
[resent since the list server seems to work again now] Am 14.02.2018 um 03:00 schrieb Kenneth Garges: > >> On 10Feb 2018, at 1:29 PM, Tilman Schmidt wrote: >> >> Any chance of checking on the firewall what's happening with the connection? > > Looking at the firewall rules show it will pass anyt

Re: [Bacula-users] Restore to Windows client fails if file is too big

2018-02-18 Thread Jose Alberto
Hi. 09-Feb 13:38 core-prod-bkp-3-sd JobId 170: Fatal error: read.c:176 Error sending data to Client. ERR=Broken pipe You check comunications (persistent conections) on you firewall or switch layer 3. You view parameter: Heartbeat Interval = 60 On file-daemon, Storage-daemon and dir ref: h

Re: [Bacula-users] Restore to Windows client fails if file is too big

2018-02-15 Thread Kenneth Garges
> On 10Feb 2018, at 1:29 PM, Tilman Schmidt wrote: > > Any chance of checking on the firewall what's happening with the connection? Looking at the firewall rules show it will pass anything on ports 9101-9103 between the hosts. I have no reason to doubt that since backups work; only restores

Re: [Bacula-users] Restore to Windows client fails if file is too big

2018-02-10 Thread Tilman Schmidt
Am 10.02.2018 um 01:01 schrieb Kenneth Garges: > Backups work fine. Restores work fine if the file I restore is small (I > have done 192 byte files as a test.) But if the file is bigger (20MB) > then I get a broken pipe error.  > 09-Feb 13:38 core-prod-bkp-3-sd JobId 170: Error: bsock.c:649 Write