>
> *FD Connect Timeout = time*
> where time is the time that the Director should continue attempting to
> contact the File daemon to start a job, and after which the Director will
> cancel the job. The default is 30 minutes.
> *SD Connect Timeout = time*
> where time is the time that the Director
Thanks for your answer Kern,
I adjusted the parameters and still did not work. Spanning tree settings of
the switches where the bacula server and xenserver are connected can affect
this way?
On Wed, Jan 31, 2018 at 8:29 AM, Kern Sibbald wrote:
> In general, it is not necessary to set the keep a
In general, it is not necessary to set the keep alive time or the
heartbeat to 1 minute. That causes unnecessary network usage.
Setting them to 300 seconds (5 mins) should be sufficient in
virtually all cases.
On 30.01.2018 21:44, Elias Pereira
wro
Hello,
I thought I'd solved it, but by returning the daemons to normal execution,
the bug returned.
I researched the variable SD Connect Timeout = 180.
1) Is 180 minutes?
2) Should it be configured in the bacula-dir.conf or in the bacula-fd.conf
of the client?
On Wed, Jan 24, 2018 at 1:11 PM,
Hello,
Talking with Heitor and running some tests, I believe I was able to solve
the problem.
In the daemons, both on the server and on the xenserver client I set up the
variable *Heartbeat Interval = 60* and on the bacula server I configured
the sysctl *net.ipv4.tcp_keepalive_time = 60* entry in
> Hello,
Hello Elias,
> I make our vms backup through the bpipe plugin and the Heitor script.
> http://www.bacula.com.br/script-configuracao-bpipe-para-backup-de-to-maquinas-virtuais-xen-citrix/
> I also back up two folders from the xenserver-fd client, and when I remove the
> entry for the bpi
Hello,
I make our vms backup through the bpipe plugin and the Heitor script.
http://www.bacula.com.br/script-configuracao-bpipe-para-backup-de-to-maquinas-virtuais-xen-citrix/
I also back up two folders from the xenserver-fd client, and when I remove
the entry for the bpipe plugin the backup is d
Hello!
i have started bacula-fd with -d100 from the commandline and get the
following output in the trace file. [trace file attached]
the problem occurrs within the folling code:
get_auth = cram_md5_get_auth(sd, jcr->sd_auth_key, ssl_need);
if (!get_auth) {
Dmsg1(50, "cram_get_auth f
Hello!
Am Freitag, den 25.03.2005, 08:30 -0500 schrieb Michael Joyner:
> Are you setting up REVERSE port mapbacks?
i build the tunnels as follows:
/usr/bin/ssh -fnCNg -2 -L 9112:192.168.100.100:9102 -R
9103:backupsrv:9103 -R 9101:backupsrv:9101
[EMAIL PROTECTED]
backupsrv is the local bacula m
Am Mittwoch, den 23.03.2005, 15:06 -0500 schrieb Michael Joyner:
> >>i have read
> >>http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors
> >>carefully but got no idea what could be wrong...
> >
> > So you are 100% positive, you've checked, three or four times that
> > the passwords are
Hello!
Am Mittwoch, den 23.03.2005, 11:27 -0500 schrieb Dan Langille:
> On 23 Mar 2005 at 13:28, Chris Joelly wrote:
>
> > i use on all configs the same password value, so there are no
> > different passwords. this error message only appears on a winnt 4.0
> > server, on a w2k and a w2k3 server t
i have read
http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors
carefully but got no idea what could be wrong...
So you are 100% positive, you've checked, three or four times that
the passwords are correct?
have STOPPED than STARTED the FD daemon?
On 23 Mar 2005 at 13:28, Chris Joelly wrote:
> Hello!
>
> i get the following error messages on the bacula server:
>
> 23-Mar 13:20 backup-dir: Start Backup JobId 68,
> Job=srv-remote.2005-03-23_13.20.23
> 23-Mar 13:18 srv-remote: srv-remote.2005-03-23_13.20.23 Fatal error:
> Authorization key r
Hello!
i get the following error messages on the bacula server:
23-Mar 13:20 backup-dir: Start Backup JobId 68,
Job=srv-remote.2005-03-23_13.20.23
23-Mar 13:18 srv-remote: srv-remote.2005-03-23_13.20.23 Fatal error:
Authorization key rejected by Storage daemon.
Please see
http://www.bacula.org/ht
14 matches
Mail list logo
