See below ... On 9/25/19 7:38 PM, Andrea Venturoli wrote: > On 2019-09-25 18:42, David Brodbeck wrote: >> I'm not sure how Max Full Interval solves the problem. I have used it >> (before we switched to virtual full) but it doesn't really pertain to >> resource contention. Maybe I didn't explain the problem very well. > > I agree. > I'm *also* using Max Full Interval & co, but I fail to see how this > relates to the problem we are discussing. > > Could you elaborate on this?
Aside from waiting for the next nightly backup due to an off-line machine a major problem with having unavailable clients is that a Full could be skipped by having the job failed. Max Full Interval resolves this issue. It does not however resolve the issue that if the machine is always off during the backup window, the machine might never be backed up, which is where rescheduling can help. > > > > >> It's a minor issue, so I'm not too concerned about it. > > Yes: as I said it's not a big problem, just an annoyance. > *Not* solving the resource contention problem, but just avoiding to > nag about it would probably be enough (at least to me). Bacula is not capable of solving resource contentions itself other than trying again. > > > > bye & Thanks > av. > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
