Theoretically, the most recent versions Bacula (the Bacula Enterprise
versions) disables any Windows suspend during a backup, but I have never
actually tried it, and I am not sure if it disables the power saving
modes though.
If you figure out how to shut off such Bacula unfriendly stuff on a M
On 7/1/2016 4:30 PM, Kern Sibbald wrote:
> Hello,
>
> In general, the TCP/IP protocol that Bacula uses is extremely tolerant,
> and should retry sending packets quite a number of times before finally
> giving up. It is designed to tolerate a significant number of dropped
> packets. However, then
Hello Craig,
I forgot to mention that I implemented a feature quite a long time
ago that compensates for most poor quality (or defensive) switches
that disconnect idle lines despite the standard Internet 2 hour
delay. The feature is a directive called:
Thank you Wanderlei, Josh and Kern! Judging from Kern's and Josh's
replies, the solution is to try and find a fix on Windows and the possibly
the switches. I guess it's best just to live with the canceled jobs and
re-run them. I'd rather have good backups than incomplete ones since as
Kern indic
Hello,
In general, the TCP/IP protocol that Bacula uses is extremely tolerant,
and should retry sending packets quite a number of times before finally
giving up. It is designed to tolerate a significant number of dropped
packets. However, then there are two things that enter to screw this
up
On 7/1/2016 1:26 AM, Craig Shiroma wrote:
> Hello All,
>
> Is there a way in Bacula to prevent something like a 1 or 2 second
> network glitch from cancelling Window Server backups? RHEL backups
> seem to survive these episodes with no problems.
>
Bacula expects DIR-to-FD and FD-to-SD TCP conne
Hello All,
Is there a way in Bacula to prevent something like a 1 or 2 second network
glitch from cancelling Window Server backups? RHEL backups seem to survive
these episodes with no problems.
Respectfully,
Craig
--
Att
