Hello Dan, On 1/18/21 16:06, Dan-Gabriel CALUGARU wrote: > Hello Eric, > > Thank you for your quick answer. > > My version of the Bacula install that I "inherited" is 9.2.1 and I > thought I can use it as it didn't seem to me really that old (it dates > from autumn 2018). > > Indeed, concerning MaxRunTime, by comparing the Bacula Main Reference > guides for the last stable versions (9.2.x, 9.4.x, 9.6.x), I saw that it > is was when passing from 9.4.x to 9.6.x that "6 days" has been replaced > by "200 days" as the time period after which watchdog thread will kill > any Job. > > Therefore, if there is no other suggestion, I think I will consider the > upgrade to the last stable version (9.6.7) to solve my problem (the > other alternative would be to split each volume in several FileSets and > launching several jobsin order to not exceed 6 days per job)
It is an other possibility that can be very nice, long jobs has the tendency to be difficult to manage (anything can happen during this 6 days), if you can have 7 parts that you backup individually, you would reduce the total data to something like 1/7 * total + 6/7 * incr_size. If the incremental size is about 10% of the total, it becomes very interesting. Best Regards, Eric _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users