This actually is a hardcoded "sanity" check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and what needed to be changed. We have no jobs that run more than a few days so have not made such changes ourselves so I can't guarantee it'll fix your problems completely - all I know is that overcoming the 6 day limit definitely will mean making a few tweaks to the code. You may want to submit a bug report and make the case that such a "sanity" check should be removed or have an configurable way to override.
hope this helps, --tom > but still they are terminated after 6 days: > > 14-Jul 20:27 cbe-dir JobId 39969: Fatal error: Network error with FD > during Backup: ERR=Interrupted system call > 14-Jul 20:27 cbe-dir JobId 39969: Fatal error: No Job status returned from FD. > 14-Jul 20:27 cbe-dir JobId 39969: Error: Watchdog sending kill after > 518426 secs to thread stalled reading File > > I like to know how to fix this. > > I've seen the comments in the mailing list in the past that running > backups that take more than 6 days is "insane". They're wrong in my > environment. I don't want to hear that again. I have a genuine reason for > running very long backups and I need to know how to make it work. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users