Rarely on our Bacula setup some (mostly Full) job fail with:
26-Jan 21:55 lnfbacula-dir JobId 16375: Error: Director's connection to SD for
this Job was lost.
26-Jan 21:55 lnfbacula-dir JobId 16375: Fatal error: Network error with FD
during Backup: ERR=Connection timed out
26-Jan 21:56 lnfbacula-dir JobId 16375: Fatal error: No Job status returned
from FD.
26-Jan 21:56 lnfbacula-dir JobId 16375: Error: Bacula lnfbacula-dir 9.4.2
(04Feb19):
Trying to understand, we think could be:
1) a (transient) network trouble
2) a (transient) peak load on SD
3) a (transient) peak load on FD
Note that 'network' mean 'LAN': FD and SD are on the same LAN; only DIR is
on a remote site, but error roughly never happen on, for example, attribute
sending (attribute spooling enabled) that involve WAN.
There's some way to have bacule a bit more 'resiliant' on these?
Currently i have on director:
FDConnectTimeout = 5 min
SDConnectTimeout = 5 min
but seems to me a pretty decent time...
Thanks.
--
Ci vuole sempre qualcuno da odiare per sentirsi giustificati
nella propria miseria. (Umberto Eco)
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
