we also tried something in this direction, how ever, there's a problem: since one cannot configure a backup job being the "successor" of another one, the time schedule has to be "guessed" somehow. This does not work reliably at least for us, sometimes jobs take longer than expected, or longer...