Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Network\s+errors\s+during\s+backups\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Network\s+errors\s+during\s+backups\s*$/: 2 ]

Total 2 documents matching your query.

1. [Bacula-users] Network errors during backups (score: 1): Author: Timur Batyrshin <erthad AT gmail DOT com>; Date: Mon, 17 Mar 2014 14:04:07 +0400; Hi all, I have a setup when Bacula Director is hosted on AWS while one of bacula clients is hosted elsewhere and I quite often see the errors like this (for backup jobs): 2014-03-17 07:25:04 XXX-sd; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2014-03/msg00107.html (14,174 bytes)
2. Re: [Bacula-users] Network errors during backups (score: 1): Author: Josh Fisher <jfisher AT pvct DOT com>; Date: Mon, 17 Mar 2014 07:22:55 -0400; Bacula expects the TCP connection from Dir to FD to remain up during the entire job. Even with the heartbeat, it is possible that some router between the two is dropping the connection or there is an; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2014-03/msg00108.html (14,929 bytes)

Current List: 1 - 2
Page: [1]