> Sent: 05 March 2009 17:38
> To: Janco van der Merwe
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] FD Error On Backup
>
> Janco van der Merwe wrote:
>> Silly question what would be an advisable / recommended heartbeat
>> interval for
3000
> Direct: 011 541 3073
> Cell: 083 291 8536
> Fax: 0866308032
>
>
> -Original Message-----
> From: Chad Walstrom [mailto:che...@wookimus.net]
> Sent: 05 March 2009 18:02
> To: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] FD Error On Backup
ngille.org]
Sent: 05 March 2009 17:38
To: Janco van der Merwe
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] FD Error On Backup
Janco van der Merwe wrote:
> Silly question what would be an advisable / recommended heartbeat
> interval for the FD and DIR, respectively
t: 011 541 3073
Cell: 083 291 8536
Fax: 0866308032
-Original Message-
From: Chad Walstrom [mailto:che...@wookimus.net]
Sent: 05 March 2009 18:02
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] FD Error On Backup
Janco van der Merwe wrote:
> Silly question...
Janco van der Merwe wrote:
> Silly question what would be an advisable / recommended heartbeat
> interval for the FD and DIR, respectively?
We set up the heartbeat for any client-server session that exists over a
firewall (which more often than not time out long-running sessions with
littl
t; Dunns Stores (Pty) Ltd
> Switch Board: 011 541 3000
> Direct: 011 541 3073
> Cell: 083 291 8536
> Fax: 0866308032
>
>
> -Original Message-
> From: Dan Langille [mailto:d...@langille.org]
> Sent: 03 March 2009 08:06
> To: Janco van der Merwe
> Cc: bacula-us
Message-
From: Dan Langille [mailto:d...@langille.org]
Sent: 03 March 2009 08:06
To: Janco van der Merwe
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] FD Error On Backup
Janco van der Merwe wrote:
> Hi All,
>
>
>
> I have this error which started after hard
Janco van der Merwe wrote:
> Hi All,
>
>
>
> I have this error which started after hardware upgrade of our MIS system
> and I can’t fix it. I went through the archive and a lot of people, who
> previously had this same problem, suggested that it might be network
> hardware i.e. Network cable
Hi All,
I have this error which started after hardware upgrade of our MIS system and
I can't fix it. I went through the archive and a lot of people, who
previously had this same problem, suggested that it might be network
hardware i.e. Network cable, switch, router, NIC - related but in my case