On 25 September 2013 21:25, Mauro wrote:
> On 25 September 2013 21:20, Mauro wrote:
>
>>
>> On 25 September 2013 18:24, Tim Krieger wrote:
>>
>>> We ran into this issue when we replaced all our iptables firewalls with
>>> Juniper SSG devices. Check the timeout values for the service you defined
On 25 September 2013 21:20, Mauro wrote:
>
> On 25 September 2013 18:24, Tim Krieger wrote:
>
>> We ran into this issue when we replaced all our iptables firewalls with
>> Juniper SSG devices. Check the timeout values for the service you defined
>> on your juniper for your bacula ports, the jun
On 25 September 2013 18:24, Tim Krieger wrote:
> We ran into this issue when we replaced all our iptables firewalls with
> Juniper SSG devices. Check the timeout values for the service you defined
> on your juniper for your bacula ports, the juniper will have a default
> session time, we found t
having to disable
the timeout feature for the bacula services.
-Original Message-
From: Clark, Patricia A. [mailto:clar...@ornl.gov]
Sent: Wednesday, September 25, 2013 7:17 AM
To: bacula-users
Subject: Re: [Bacula-users] fatal error on full backup.
From: Mauro mailto:mrsan
From: Mauro mailto:mrsan...@gmail.com>>
Date: Wednesday, September 25, 2013 8:18 AM
To: Uwe Schuerkamp
mailto:uwe.schuerk...@nionex.net>>, Mauro
mailto:mrsan...@gmail.com>>, bacula-users
mailto:bacula-users@lists.sourceforge.net>>
Subject: Re: [Bacula-users] fatal erro
On 25 September 2013 13:58, Uwe Schuerkamp wrote:
>
> On Wed, Sep 25, 2013 at 01:01:41PM +0200, Mauro wrote:
>
> > Start time: 25-Sep-2013 10:55:01
> > End time: 25-Sep-2013 12:55:26
>
> This looks suspiciously close to 7200 seconds which is the default
> tcp_keepaliv
On Wed, Sep 25, 2013 at 01:01:41PM +0200, Mauro wrote:
> Start time: 25-Sep-2013 10:55:01
> End time: 25-Sep-2013 12:55:26
This looks suspiciously close to 7200 seconds which is the default
tcp_keepalive_timeout for most Linux distros.
Have you tried using the bac
Hello.
I'm doing a backup of a single host.
Data is about 57G.
Bacula server is 5.2.6 in a debian linux system with 8G of ram.
Database is postgresql on the same server.
Job seems ending normally:
status client=svsostream01-fd
Connecting to Client svsostream01-fd at 192.168.240.10:9102
svsostream
